[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Proposed features

On Mon, 2008-02-11 at 14:57 +0100, Tim Lauridsen wrote:
> Jakub 'Livio' Rusinek wrote:
> > Hi,
> > 
> > I proposed some features for Fedora. They might not be accepted, but 
> > it's worth a try.
> > 
> > * http://fedoraproject.org/wiki/JakubRusinek/DRAFT%3A1clickInstall
> I have made a little app doing the same stuff.
> bzr branch http://timlau.fedorapeople.org/bzr/easyinst
> cd easyinst
> sudo ./easyinst.py app.ini
> it is using an ini file instead of xml looking like this
> [livna]
> type=repository
> method=rpm
> url=http://rpm.livna.org/livna-release-8.rpm
> [gstreamer-plugins]
> type=addons
> name=Gstreamer plugins to play MP3,Xvid etc.
> desc=Gstreamer plugins to play MP3,Xvid etc.
> method=yum
> repo=livna
> packages=gstreamer-plugins-bad,gstreamer-plugins-ugly
> [nvidia]
> type=drivers
> name=Nvidia Drivers
> desc=Nvidia Closed Source Driver with 3D support.
> method=yum
> repo=livna
> packages=kmod-nvidia
> [yumex]
> type=application
> name=Yum Extender
> desc=A GUI for the yum package manager
> method=yum
> It is very easy in development, but it works.
> Tim
Just my 2 cents what I would expect it to behave like.

1. User double-clicks on the settings file (in this case app.ini)
2. EasyInst is executed with the app.ini as parameter
3. EasyInst Checks whether the required repository is installed
  3.a. if not, wgets the settings rpm and run it with
       system-install-packages (or PackageKit implementation)
4. If successful, install the packages with system-install-packages (or
   PackageKit implementation)
5. Tada, user has what he wanted.

For steps one and two, we'd need to assign easyinst to some mime-type,
dunno if it would work as expected for ini files... I'd suggest
something like applications/x-easyinstall and associate it with .einst

The goal of steps 3 and 4 is, that the user will have to interact with
graphical installer, if there is any interaction needed, and will be
informed when the process is finished. But perhaps this could be done
different way...


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]