[clbuild-devel] `clbuild lisp' and `asdf:*central-registry*'...

[Dietrich Bollmann]

Hi David,

On Tue, 2008-03-04 at 20:00 +0100, David Lichteblau wrote:
> Hi,
> 
> Quoting Dietrich Bollmann (diresu at web.de):
> > I read on clbuild's homepage ( http://common-lisp.net/project/clbuild/ )
> > that `~/.sbclrc' is ignored when starting sbcl with `clbuild lisp'
> > when not explicitely told to use it by creating the file
> > `clbuild/clbuild.conf' using `clbuild/clbuild.conf.default' as a model
> > and setting the variable `USER_INIT' to something like
> > `${HOME}/.sbclrc'.
> >
> > But even when doing so, my configured version of
> > `asdf:*central-registry*' would be ignored.
> 
> good point.  I have added a new configuration variable called
> SETF_CENTRAL_REGISTRY, which can be overridden in clbuild.conf.  It's
> just a simple boolean flag for now to switch between SETF and PUSH.

Thanks.  But this doesn't allow to change the position of the 
clbuild path in the registry which could be usefull if some 
private installation of a package should be prefered to a 
different instance of the same package later in the path.

How about a third option which just leaves the registry as it 
is specified in the profile?  (Actually I feel like this should 
be the default as to me it is strange that some values from the 
profile later are overwritten even if the user explicitly 
configured clbuild to use the profile.)

By the way, what do you think would be the best way to test 
in the profile if a running sbcl is the one installed with 
clbuild or some other installation?  Currently I am using a 
different profile for the clbuild version and specifying 
`USER_INIT=${HOME}/.sbclrc-clbuild' in clbuild.conf.  

I would prefer to decide upon different initialisations in 
the profile by using something like 

  #+sbcl #-sbcl-clbuild (do-something)
  #+sbcl #+sbcl-clbuild (do-something-different)

> > PS: Probably a better way would be to set 'asdf:*central-registry*' to 
> > the value needed by clbuild before the profile is loaded.
> 
> Hmm...

Isn't this what lisp also does normally?

When using the sbcl or cmucl package in Debian for example the 
value of asdf:*central-registry* is already initialised with the 
standard Debian lisp package installation paths and other paths 
can be prepended / appended / inserted or the value can be overwritten.  
When using clbuild all default packages should be in clbuild/systems 
as far as I understand.

Thanks, Dietrich

> _______________________________________________
> clbuild-devel mailing list
> clbuild-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/clbuild-devel
>