Re: Little redesign of package files for 1.3

2008/5/28 Isak Savo <[email protected]>:
> On Wed, May 28, 2008 at 7:37 PM, Thomas Leonard <[email protected]> wrote:
[...]
>> But is that really what we want in the future? Take an Autopackage
>> program like Stellarium (the link on the site is broken, BTW). Using AppArmor /
>> SELinux / Plash / whatever, we can quite easily say that it should get
>> write access only to ~/.stellarium, and it will run fine if installed using a
>> more-trusted external program (e.g. Zero Install).
>>
>> But if the package includes the installer, it needs write access all over
>> the place, including the ability to change my menus, add things to $PATH,
>> etc.
>
> I'm not sure I'm following you here.. how would you then get stuff
> like icons in the menus, path changes to the new program etc to work?
> Or do you mean that the package calls external, trusted apps to do
> this?

If the installer is separate then you start by running the installer, not the
package. For example, to add ROX-Filer to the Ubuntu Application's menu,
you:

1) run Applications -> Add Zero Install Program
2) drag http://rox.sourceforge.net/2005/interfaces/ROX-Filer to the dialog box

You end up with an item in your menu for launching ROX-Filer, but the package
itself doesn't know anything about menus.

There's a video here (with audio) showing how that works:

http://www.youtube.com/watch?v=Lu0MAiNIaGM


-- 
Dr Thomas Leonard	http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1

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