Re: [Chicken-users] Installing data files for eggs

[Jim Pryor]

On Sun, Oct 03, 2010 at 01:02:01AM +0200, Peter Bex wrote:
> > -(define style-path
> > -  (list (installation-prefix) "share" "chicken" "slatex"))
> > +; also declare additional dependency on setup-helper
> > +(include "setup-helper")
> > +(define style-path
> > +  (list (installation-chicken-home) "slatex"))
> 
> That's perhaps slightly better from a readability point of view, but
> installation-chicken-home is just an alias for
> {installation-prefix}/share/chicken so in reality all this does is
> add a depedency on the setup-helper egg.

Oh, I see, yes you're right. I had just assumed that
(installation-chicken-home) honored the $DATADIR.


> > 2. And that's where you should be copying your slatex.sty etc. files. Is
> > it really true that files copied in that way don't get uninstalled by
> > chicken-uninstall?
> 
> Yes, the install-* procedures register their files in a database.
> Chicken-uninstall simply looks there and removes all registered items.
> The procedure that does this (write-info) is not exported by the
> setup-api, so this simply cannot be done from custom code.

I didn't know whether the copy-file procedure also registered files in
that database. I gather from what you're saying that it does not.


> > When building a package, we run:
> > 
> >     chicken-install -p /some/fakeroot/usr
> > 
> > This installs all the egg's files underneath an (otherwise empty) fakeroot. 
> > If the build step completes successfully, then the packaging system 
> > compresses all the files in the fakeroot and wraps it as a binary package. 
> > Later, the user can install that binary package and the files will then be 
> > installed not underneath /some/fakeroot, but instead underneath the real 
> > root /.
> 
> Looks like DESTDIR support.

Exactly.


-- 
Jim Pryor
address@hidden