Re: /package registration

Stefan Karrmann <[email protected]> wrote:
> Only root can/should insert a new package in slashpackage and
> /command.

I'd say that's a policy decision outside the scope of the
specification of /package.  Admins can make category directories
group- or world-writable if they like; they're already sticky.

> o source directory - where is the source
> o build directory - where to compile the source
> o destination directory - where to put the source
> o run directories of used programs - where are they on the running system

I think one configuration parameter might be sufficient, and we
definitely don't need more than two.  Source, build, and destination
directories all have fixed names in a common parent directory.  If you
want to move them for some reason, you can just leave symlinks behind.

> Note, that dstdir and rundir (of the package itself) may be different for
> cross compilations and package builds.

For cross-compilation, maybe.  What do you mean by "package builds"?

> If any user can choose run directory as he likes it, he can build his
> own package collection with his own registry and renaming.

Right, but it's also good to have a global registry, so users don't
have to sort out conflicts themselves if they don't want to.


paul