Re: Autopackage frontend

Ah ok. So the program package takes care of all the installation and
uninstallation?
But I still don't quite get how to use that protocol. Do I need to read from
"bla.package" when I execute "package install bla.package"? And when I run
"package install bla.package", how can I prevent it from poping up the GUI?
Because I would like to use my own GUI.
Hylke


On 9/13/07, Eugene Zolenko <EugeneZolenko-XYgkjQFSZqy1Z/[email protected]> wrote:
>
> > And how does uninstallation work, because i couldn't find that either.
>
> > Because I can imagine that you don't want to download a
> > autopackage file to uninstall it. And how does the autopackage now it
> > should be uninstalled?
>
> The uninstall of a package is triggered with
> #package remove $SHORTNAME
>
> (or via "manage 3rd party apps" GUI).
>
> If you need implementation details (which users don't care about, and
> packagers shouldn't either, although sometimes have to :)):
>
> Anything that passes through logCommand is added to uninstall log.
> (standard autopackage APIs like copyFiles, mkdirs, logFile and so on use
> logCommand underneath).
>
> The log is then executed inside uninstallFromLog function. Which is
> usually located in uninstall section of a package.
>
> So package like this:
>
> [install]
> touch /tmp/somefile
> logFile /tmp/somefile
>
> [uninstall]
> uninstallFromLog
>
> Will have
> removeFile /tmp/somefile
> in its log.
>
> The log and uninstall script for installed package located in
> /var/packages/$SHORTNAME/log
> /var/packages/$SHORTNAME/uninstall
> (Assuming default root installation of support code).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
> For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
>
>