scsh-hackers
[Top] [All Lists]

Re: [Scsh-hackers] Stand-alone installation library

To: Michel Schinz <Michel.Schinz@epfl.ch>
Subject: Re: [Scsh-hackers] Stand-alone installation library
From: Martin Gasbichler <gasbichl@informatik.uni-tuebingen.de>
Date: Mon Mar 29 04:31:02 2004
Cc: scsh-hackers@lists.sourceforge.net
List-id: Discussion among the implementors <scsh-hackers.lists.sourceforge.net>
Sender: scsh-hackers-admin@lists.sourceforge.net
Michel Schinz <Michel.Schinz@epfl.ch> writes:

> Hi,
>
> Since the release of the packaging proposal is approaching, there is
> one last thing I'd like to "clean up", namely the way the installation
> library is distributed.
>
> As you know, the initial idea was that the library would be
> distributed along with every package, but Daniel Kobras said it would
> be better to have a separate distribution, and I think he is
> completely right. As discussed here, I think it's best to start with a
> stand-alone distribution, and maybe package everything with scsh later
> (or maybe sunterlib, as Anthony suggested, we'll see).
>
> Anyway, I've now prepared a stand-alone distribution of the library.
> This distribution basically packages the documentation, the
> installation library and the new "scsh-install-pkg" script which does
> what "install-pkg" used to do.
>
> This change implies a few changes for package authors, which can be
> summarized as follows:
>
>   - you should not distribute the installation library with your
>     package anymore, but rather explain how and where to get it (I'll
>     prepare a standard README file soon to explain that, which you'll
>     then be able to include with your packages),
>
>   - the file "pkg-def.scm" must now be in a standard location, namely
>     at the root of the package unpacking directory (it used to be that
>     "install-pkg" had to be there, but this one moved to the
>     installation library now).
>
> (I'm sorry for asking for these changes so late... If some of you
> would like me to perform these changes myself, I can of course do it
> [where I have CVS access, that is]).
>
> The stand-alone installation library can now be found on my page, at
> the following address:
>
>   http://lamp.epfl.ch/~schinz/scsh_packages/
>
> There you will also find a "package kit" for SSAX, which makes it
> possible to install SSAX 4.9 as a scsh package.
>
> I'd be glad if some of you had time to check what I did and say what
> they think about it. This can be considered as the first beta, in
> fact.

I successfully installed sunterlib and sunet from CVS, your SSAX
package, and the scx tarball from

<ftp://ftp.scsh.net/pub/scsh/packages/scx/scx-0.2-beta.tar.gz>

and everything worked very smoothly. I'm very happy with the packaging
proposal and the installation library!


One small remark: The scripts displays the following message at the
end of the installation process:

In order to use them, make sure to add the following value
to the environment variable SCSH_LIB_DIRS (quotes included):
"some/path"

This might be disturbing for users who use configure's
--with-lib-dirs-list option (as they don't need to set SCSH_LIB_DIRS).


-- 
Martin


<Prev in Thread] Current Thread [Next in Thread>