Re: Little redesign of package files for 1.3

On Wed, May 28, 2008 at 7:52 PM, Jan Niklas Hasse <[email protected]> wrote:
> On Wed, May 28, 2008 at 7:28 PM, Isak Savo <[email protected]> wrote:

>> The difference being that with autopackage you actually *can* run the
>> install scripts as $user, which you can't with rpm and deb :)
>
> I think it would even be possible to install a package as root without
> actually running any of its code as root. Packagers could still make
> flexible packages, but should do that in the Prepare section. The
> actually copy/move part to the prefix should be autopackages job.

Hmm, I was gonna reply with the argument that packages need
programming logic inside [install] but after reviewing a few of our
own apspecs, I see that most logic is actually inside [Prepare] or
[PrepareBuild] (the latter isn't even run on the users system)

It *would* however, break all existing packages if we removed the ability :(

> The idea behind installEverything is the following: When I created a
> package for a program i realized, that calling the right function
> inside the  [Install] section is a job, which could be easily made by
> a script (and makepackage creates the Install section for you if you
> leave it blank afaik). So my idea is, to remove the [Install] section
> completely, I don't see a case where it is really needed. Instead of
> calling
>
> installBin mybinary
>
> i could call
>
> mv mybinary bin/mybinary
> inside Prepare.

That would work for installExe, but how would you fix installIcon or
installMime? That's literary hundreds of lines of code, written with
years of testing on various distributions. It's way more than a simple
mv

-Isak

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