Re: Autopackage installation systemwide/local

On Sun, Apr 6, 2008 at 2:04 PM, Hylke Donker <[email protected]> wrote:
>
>
>
> On Sat, Apr 5, 2008 at 5:50 PM, Isak Savo <[email protected]> wrote:
> >
> > On Sat, Apr 5, 2008 at 5:19 PM, Hylke Donker <[email protected]>
> wrote:
> > > On Sat, Apr 5, 2008 at 5:13 PM, Isak Savo <[email protected]> wrote:
> > > >
> >
> > > > No, there are no such argument. And frankly, why would there be one?
> > > >
> > > > It's the user that is making the installation, and if that user wishes
> > > > to install as root, (s)he can:
> > > >  a) run as root directly (sudo/su -c)
> > > > or
> > > >  b) enter the password when asked for by autopackage
> > >
> > > I have autopackage embedded in my program(the frontend is intergrated in
> my
> > > program). I know whether the user chose to install a package system-wide
> or
> > > local, but I wanted my patches to be properly installed. For example, if
> the
> > > user chose to install the package locally, I don't want the user to
> install
> > > the patch system-wide.
> >
> > I'm not sure I understand what you mean with patches. Are they
> > upgrades of existing packages or are they separate packages (different
> > rootname) that are installed "on top" of already existing packages?
>
> They are seperate packages that are installed ontop of existing packages,
> since I didn't know a better way to install updates.
>

Hmm... Maybe we should fix that by providing a "UpdateFor:" option to
the meta section that takes an root name and says, that this package
can only be installed over the specified version. What do you think?
Should we add the parameters to the package command anyway?

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]