Re: Choosing a package name

Stefan Karrmann <[email protected]> Wed, 7 Aug 2002 03:53:47 +0200
Newsgroups gmane.comp.djb.package
Message-ID <20020807015347.GB388@johann>
Paul Jarc schrieb folgendes am Sun, Aug 04, 2002 at 07:08:20PM -0400:
> "Stefan Karrmann" <[email protected]> wrote:
> > If 2002/admin/daemontools are disappers, we can use the name
> > 2004/admin/daemontools, etc. to denote a NEW package with similiar
> > functionality.
> 
> Who are "we"?  Are programs to be expected to look for both?  What
> benefit does this naming scheme provide?  If 2002/admin/daemontools is
> registered for one package, is 2004/admin/daemontools still available
> to be registered for another package?  If not, what does this provide
> that we don't already have with versions?

"We" means the community of /package users.
The programs need not to look for both, since they name different packages!

Every year a new prefix comes into use, i.e. year/.
Only the packages newly registed in this year are prefixed with it.

Suppose that admin/daemontools ist created in 2002, gets a few
updates and becomes unsupported by 2004. Then for ETERNITY this name
is blocked! I.e. NOBODY could reuse the name, he must choose something
like admin/daemontools2, admin/daemonutils, admin/daemontools-of2005, etc.
Till the end of eternity, this could happen very often. Of course, the
last name, using a suffic, is similiar to my proposal and solves the
problem, too. It even has the advantage of an "a posteriori"/"as needed" solution.

Eventually, I see that no need to force a new name convention.

-- 
Stefan Karrmann