Re: Choosing a package name

Paul Jarc schrieb folgendes am Sat, Aug 03, 2002 at 09:17:20PM -0400:
> Stefan Karrmann <[email protected]> wrote:
> > 1. Use /package/host/localhost.
> 
> A different area of /package/host would be better, if you have a
> publicly registered domain.

Right, but I don't have any.

> >    But then I have to move most of them upwards after registration
> >    which increases the work.
> 
> Just leave a symlink in the old location pointing to the new one.
> Remove it when there are no longer any packages relying on the old
> name.

Right.

> > 3. Use naming like `registration_year:name', e.g.
> >    `2002:admin/daemontools'.
> 
> I don't see what benefit this is supposed to provide.  (Nit: colons
> are prohibited in package names.)

If 2002/admin/daemontools are disappers, we can use the name
2004/admin/daemontools, etc. to denote a NEW package with similiar
functionality. Of course you can name the new one admin/daemontools-of2004
or admin/daemontools-nt ...
Personally, I would the common prefix of the registration year.



> > 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.
> 
> I don't think we need them to be *that* small.

Well, there may be 1521 enties per directory do call this still small?

-- 
Stefan Karrmann