Policy for package contents (Was: Re: Choosing a package name)

Paul Jarc schrieb folgendes am Sun, Aug 04, 2002 at 07:03:15PM -0400:
> Stefan Karrmann <[email protected]> wrote:
> > PS: Is there a policy for packages besides the example admin/daemontools?
> 
> For the contents, you mean?

Yes.

> We have package/versions and
> package/sharing.  I also think the descriptions in package/INSTALL in
> my packages would be useful conventions.
                              ^^^^^^^^^^^ Right, where are they published?

But where are registered/public/private commands, shared libraries,
include files, etc.?

The directory command for registed commands seems to be convention
and it may be useful for sptools to check /command.

If every package put its public, non-registered commands in another
place, this will be very confusing, e.g. c, cmd, cmd-pub, cmd-loc, etc.
Of course, a user of a package should KNOW where these commands, etc.
are. But, a policy may recommend additional files, e.g.:

command-public  for non-registed commands provided by the package
command-private for private (often changing) names
library-public-shared  for dynamic libs, needed by clients at runtime
library-public-static  for libs (and includes = interfaces),
                       needed by clients during compilation
library-public-source  for source libs.

package/package-name     the package name
package/package-version  the version

Comments?
-- 
Stefan Karrmann