Re: registration request

Paul Jarc (Mon, Apr 14, 2003 at 01:48:17PM -0400):
> Stefan Karrmann <[email protected]> wrote:
> > <http://stka.port5.com/package/data/nstrtools>
> 
> The data/ directory in the tarball isn't sticky.

Fixed in data/nstrtools-1.0.1 (to appear). Thanks.

> You have no package/install script.  (I know, I'm guilty of this too
> in my latest versions.  The new mkmed fixes this and is almost ready,
> if you're interested in using it.)
> 
> You have no package/sharing file.  (mkmed could generate one for you.)

Are these required for /package? Where should the commands copied or
symlinked to? Most of the subsets of {1,..,7} makes sense where
(1) /command
(2) /bin
(3) /sbin
(4) /usr/bin
(5) /usr/sbin
(6) /usr/local/bin
(7) /usr/local/sbin

Of course, the choice should be denoted in conf-compile/install or alike.
Then package/install makes sense.

> The instructions mention editing files in compile-conf/, but that
> directory does not exist.  It would be best if we could run
> package/compile without editing any files to build with default
> options.

Well, I've renamed compile-conf to conf-compile but I had forgotten to
update doc/install.html. Sorry.

You always have to make some assumptions about the environment if you
run 'sh package/compile'.
If you run 'sh package/addenv2conf-compile' the current environment
is inspected and conf-compile/. is completed as far as possible.
Later runs of 'sh package/compile' only relies on information in
its own directory tree. (Well, this is my plan - now gcc etc. are
still needed to be in the PATH.)

> My packages currently put compile-time configuration files in
> preconf/.  It would nice to have consensus here.  What do people think
> the name should be?

preconf/. is a pretty short name, but 'preconf' does not say that its
contents must be provided before _compilation_. It may be prior to
setting up a demon, etc.

> How should configuration files affect sharability?  I think
> compile-time configuration should be "dist" (or maybe "syst"?) and
> run-time configuration should be "host".

The reason for package/sharing is that the installer can choose
the sharing of sub directories. The package may suggest defaults in
package/sharing but an installer can ignore these hints. If the package
has different sharing suggestions for similiar data it has to put it
into different directories and add a line to package/sharing.
Thus, you can do it as your packages need it.

Sincerly,
-- 
Stefan Karrmann