Choosing a package name

Hi folks!

After reading http://cr.yp.to/slashpackage/names.html I am still unsure
about good names.
A long term project of mine is to compile all needed packages locally
and force them into the slashpackage hierarchy. (Well, I'll create
small installer packages which use the original ones.) This will
generate thousends of packages, c.f. www.debian.org. They will consume
many GLOBAL names for eternity, even if they disappear in a year (or so).

How can this be avoided? Answers:

1. Use /package/host/localhost.
   But then I have to move most of them upwards after registration
   which increases the work. Global names are for global packages, so
   the stable ones should be registered.

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'.

others...

What is the policy? Where is/will it (be) documented?


My first package will be: editor/ed-spi0.2
With commands: ed red

It is a slashpackage installer (spi) for ed-0.2.
It conflicts (naturally) with the commands of (GNU) ed.
As soon as the FSF improves ed-0.2 or supports slashpackage,
ed-spi0.2 will be obsolete.
There may exist alternative implementations of ed (e.g. sun, ibm, etc.)
As soon as there is an `alternative selection tool' (per host or even
per user) I will revoke the GLOBAL commands (ed, red) and provide them
as LOCAL commands.

PS: If you really want to keep directories small, you should use many
    slashes, e.g. 20/02/:a/dm/in/da/em/on/to/ol/s-/0./72 or even a
    slash after every byte.
-- 
Stefan Karrmann