On Wed 07 Jan 2009 at 10:20AM, Stephen Hahn wrote:
> 
>   For most of the Fridays in the fall, I would iterate randomly through
>   the packages on my laptop, proposing a new package name based on the
>   scheme from last spring.  Eventually, I renamed everything, and then
>   started writing checks to make sure groups of names appeared to be
>   self-consistent.  Once that was done, it was just before winter break,
>   but Rich B has asked me for this a few times, so I'd better disgorge
>   it.
> 
>   I've attached the script and the .pkl file with the renames, in case
>   anyone wants to add new convention tests to see the impact.  There are
>   some unsettled questions about some of the common package basenames,
>   like "base", "core", and "extra".  It may be preferable to not allow
>   these, and to force them into the role of suffixes--so
>   "something-base" rather than "something/base".  Unique basenames make
>   pkg(1)'s abbreviation matching work directly.
> 
>   Also, I've used "feature/" generally to mark current packages that
>   we should consider breaking up.  The use is not consistent with the
>   precise usage in Mike G's post, and is not meant to remain in use once
>   we determine the future boundaries of the relevant packages.
> 
>   So, included below, is the output of the renaming script for about 671
>   packages.  It should be enough to trigger discussion.

Does a package's occupation of a slot in the namespace also preclude
descendants?  (either by convention of by proposed code changes?)

That is to say, if system/font/x11 is a package, is it impossible (or
ill advised) to have system/font/x11/supplemental ?

At a higher level-- how do I know what is a category versus what
is not a category?  How much work do you anticipate we will put
into the tools around knowing that "/" is a delimiter?  That is
to say, given "print/a2ps", would "pkg install a2ps" be expected
to work, assuming a2ps is unambiguous?

> gcc-dev -> 'feature/develop/gnu'
>       GNU Tools Development cluster

I think this is somewhat hard to understand.  Perhaps preserving
some of the flavor of the thing in the last path element would be
nice:

        feature/develop/gnu-dev

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - [email protected] - blogs.sun.com/dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to