Re: Autopackage installation systemwide/local

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?

In any case, since you have the frontend embedded (did you develop one
yourself or are you using one of ours?), you could at least force a
system wide install by making the user run the installer through sudo.

Autopackage does some sanity checking when upgrading packages. It is
for instance not possible to upgrade a system wide installed package
with one installed as a user.

I'm starting to see a use case here for your request though... I'm
just wondering whether a command line switch is the best option or if
it should be controllable by the frontend somehow.

-Isak

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