As I said in my previous e-mail, I'd like to discuss the packaging of
third-party modules for scsh.
My aim is to provide Fink packages for sunet and sunterlib in the
future, and the main problem I'm facing right now is the lack of a
standard installation procedure for these packages. Sunet, for
example, doesn't provide a Makefile to install anything, while the
Sunterlib provides a Makefile which puts Scheme files in
$prefix/lib/sunterlib and documentation in
$prefix/share/doc/sunterlib.
To ease the packaging of such third-party modules, I think it would be
a good idea to define a standard for them, and to document that
standard in the scsh manual. This standard should specify things like:
- the directories in which files should go (this should be a
relative directory, for example $prefix/lib/scsh/modules),
- the command(s) which can be used to configure and install the
files (e.g. "configure --prefix=...; make install")
- the naming scheme for important files, like the file containing
the definition of package(s), etc.
- many other things, depending how far we want to go.
With such a standard, I think it would be a lot easier to install and
use third-party modules, and of course to package them.
Comments ?
Michel.
|