Re: Choosing a package name

clemens fischer schrieb folgendes am Sat, Aug 03, 2002 at 06:55:45PM +0200:
> > Stefan Karrmann:
> 
> > 1. Use /package/host/localhost.
> > 2. Don't care. Fill up the namespace as the names come. Then in 10 years
> >    no simple names will remain...
> > 3. Use naming like `registration_year:name', e.g.
> >    `2002:admin/daemontools'.
Read it: 2002/admin/daemontools

> maybe you should create a separate name-space manager to accomodate every
> conceivable strategy.  it should enable the user to create and modify name
> spaces, including, if possible, several versions of the same package. 
But the GLOBAL name must still be registed! Then you can use it as a
(sub)directory name. If you want access by other names, you should
create a new directory containing your prefered names as symlinks to
the registered one. (It'd be nice if ALL packages can be installed in
every package repository not only /package. Then every user can create
its own repository, e.g. ~/package, and does not depend on system
administrators. This requirement should go into the policy.)

> freebsd, for example, installs several coexisting versions of tcl/tk,
> because they are incompatible.  so users must call them up by their
> respective names, but there are other benefits.

You can register them as tcl/tk-v1.42-1, tcl/tk-v2.17-1, etc.

> maybe the name spaces should be of the OO type, so that you can send its
> objects messages to identify themselves.

Do you mean, that they should respond with their global name?
Then put it into policy that .../pkg/name (or similiar) contains it.

PS: Is there a policy for packages besides the example admin/daemontools?
-- 
Stefan Karrmann