Re: /package registration

Paul Jarc schrieb folgendes am Fri, Jun 07, 2002 at 09:47:28PM -0400:
> [email protected] wrote:
> > /package/`md5sum foo-1.0.tar.gz | cut -d' ' -f1`/foo-1.0

Better use /package/f/o/o/v-1.0 if you don't want big directories.
You will never have more than 256 (plus some versions) entries per
directory. You get flexibility to symlink subtrees to different disks
if space or policy demands it. You can even encode chr(0) as %00 (URL-
scheme) and other special characters like `/' and non-printables.

Of course, you exchange directory size with directory depth and you still
need a registry for global names.

The latter leads to an problem of slashpackage. Only root can/should
insert a new package in slashpackage and /command. (Formally) I, as an
ordinary user, cannot use any of these packages for myself without
cooperation of root! Thinking about this problem I found some parameters
for package building:

During build:
-------------

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

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

The running program has only to know the run directories of all programs
(libraries, includes, docs) it uses.

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

-- 
Stefan Karrmann