From sebyte at smolny.plus.com  Thu Nov  5 16:18:01 2009
From: sebyte at smolny.plus.com (Sebastian Tennant)
Date: Thu, 05 Nov 2009 16:18:01 +0000
Subject: [clbuild-devel] elephant
Message-ID: <k4y5gd3a.fsf@vps203.linuxvps.org>

Hi all,

Any reason why wnpp-projects can't be changed to pull in elephant-1.0?

Current entry:
 elephant         get_darcs http://www.common-lisp.net/project/elephant/darcs/elephant

Required change:
 elephant         get_darcs http://www.common-lisp.net/project/elephant/darcs/elephant-1.0

Regards,

Sebastian
-- 
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap




From amynbemail-list at yahoo.fr  Thu Nov  5 20:22:40 2009
From: amynbemail-list at yahoo.fr (amynbemail-list at yahoo.fr)
Date: Thu, 5 Nov 2009 20:22:40 +0000 (GMT)
Subject: [clbuild-devel] How to install manually + Silent git error
Message-ID: <824039.45821.qm@web26601.mail.ukl.yahoo.com>

Hello all,

(Sorry for double post, please reply to this one not the other)

I installed yesterday clbuild via darcs in order to install Weblocks.
I then got a problem when auto getting "cl-base64" dependency via clbuild, so I downloaded cl-base64-3.3.3 archive and untgz'd it to source/cl-base64. Then I symlinked systems/cl-base64.asd to  source/cl-base64/cl-base64.asd.

Finally I ran "clbuild recompile cl-base64"

Could someone tell me if what I did seems sufficient to install manually a project ?


Obviously, no, because I then got a silent error when trying to run clbuild install webblocks. The process stops at cl-base64 with the following error : "error: update was interrupted".

When tracing bash script, I found that this error came from line 620 :

actual="`cd $name && git config --get remote.origin.url`"


and git returns error code 2 which exits to trapped function.

I avoided it by skipping cl-base64, but maybe a better error message could be displayed (I never used git and hence do not understand why this command is called and what it looks for exactly).



Last thing, I regularly get an error with touch trying to create "PROJECT/.clbuild-skip-update" file, but PROJECT dir does not exist. I suppose the script means to skip installed projects AFTER installation hence after creating directory ??

Thanks
-Amyn


      




From luismbo at gmail.com  Sun Nov  8 12:26:44 2009
From: luismbo at gmail.com (=?ISO-8859-1?Q?Lu=EDs_Oliveira?=)
Date: Sun, 8 Nov 2009 12:26:44 +0000
Subject: [clbuild-devel] [cffi-devel] memutil.lisp breaks compile
In-Reply-To: <639mdlou.fsf@vps203.linuxvps.org>
References: <fx8tgcly.fsf@vps203.linuxvps.org>
	<50e8e4f60911051403r4c3b235wc515a956bd4a5952@mail.gmail.com> 
	<639mdlou.fsf@vps203.linuxvps.org>
Message-ID: <391f79580911080426r2266d9e6ya5c1648c69bae160@mail.gmail.com>

On Sat, Nov 7, 2009 at 10:17 PM, Sebastian Tennant
<sebyte at smolny.plus.com> wrote:
> Lu?s is concerned about breaking things that depend on (or at least benefit
> from) his kludge (no offence intended). ?Daniel Herring makes the point that
> hijacking names to provide upgarde/compatibility layers is a time-honoured
> tradition.
>
> In my humble opinion, hijacking names works for comprehensive drop-in
> replacements based on consensus amongst parties. ?CFFI is clearly not a
> comprehensive drop-in replacement for UFFI and there's clearly no consensus on
> the issue. ?I'm therefore in favour of changing the name.

Patches for CFFI and, most importantly, clbuild are very much welcome. :-)

-- 
Lu?s Oliveira
http://r42.eu/~luis/



From pinterface at gmail.com  Sat Nov 14 02:03:04 2009
From: pinterface at gmail.com (Pixel // pinterface)
Date: Fri, 13 Nov 2009 20:03:04 -0600
Subject: [clbuild-devel] Add ASDF
Message-ID: <hdl34t$136$1@ger.gmane.org>

Because /not/ having ASDF available seems a curious oversight for a project
which relies so heavily upon it.

Well, okay, SBCL includes a copy of ASDF anyway, so it's not that strange.
But sometimes it's nice to have a central copy for all one's lisps.


patch available at
  http://web.kepibu.org/tmp/add-asdf.dpatch

The patch only makes ASDF available like any other clbuild system.  I leave
worrying about ensuring clbuild's copy of ASDF gets used when running
`clbuild slime` or `clbuild lisp`--and whether such a thing would even be a
good idea--for others.

-pix






From david at lichteblau.com  Sat Nov 14 08:09:32 2009
From: david at lichteblau.com (David Lichteblau)
Date: Sat, 14 Nov 2009 09:09:32 +0100
Subject: [clbuild-devel] Add ASDF
In-Reply-To: <hdl34t$136$1@ger.gmane.org>
References: <hdl34t$136$1@ger.gmane.org>
Message-ID: <20091114080932.GA2855@radon>

Quoting Pixel // pinterface (pinterface at gmail.com):
> patch available at
>   http://web.kepibu.org/tmp/add-asdf.dpatch

Thanks...

> The patch only makes ASDF available like any other clbuild system.  I leave
> worrying about ensuring clbuild's copy of ASDF gets used when running
> `clbuild slime` or `clbuild lisp`--and whether such a thing would even be a
> good idea--for others.

... although that is the essential part.

We already have code that downloads ASDF for the Lisp which doesn't
include it (namely clisp).  If you change that CVS invocation, I could
see the benefit of this proposal.

d.



From pinterface at gmail.com  Wed Nov 18 02:44:32 2009
From: pinterface at gmail.com (Pixel // pinterface)
Date: Tue, 17 Nov 2009 20:44:32 -0600
Subject: [clbuild-devel] Add ASDF
References: <hdl34t$136$1@ger.gmane.org> <20091114080932.GA2855@radon>
Message-ID: <hdvn2k$k8j$1@ger.gmane.org>

"David Lichteblau" <david at lichteblau.com> wrote in message
news:20091114080932.GA2855 at radon...
> Quoting Pixel // pinterface (pinterface at gmail.com):
> > patch available at
> >   http://web.kepibu.org/tmp/add-asdf.dpatch
>
> Thanks...
>
> > The patch only makes ASDF available like any other clbuild system.  I
> > leave worrying about ensuring clbuild's copy of ASDF gets used when
> > running `clbuild slime` or `clbuild lisp`--and whether such a thing
> > would even be a good idea--for others.
>
> ... although that is the essential part.

I disagree that it's the only bit which makes including ASDF interesting,
though that may be due to the quirks of my particular setup.  (A single
clbuild source tree is shared across a heterogeneous set of machines and
operating systems, so I can't generally use binaries built under clbuild.)

> We already have code that downloads ASDF for the Lisp which doesn't
> include it (namely clisp).  If you change that CVS invocation, I could
> see the benefit of this proposal.

Ha!  I seem to have missed that.  Didn't think to look for it in the shell
script.

Something more like this, perhaps?
  http://web.kepibu.org/tmp/asdf-try-2.dpatch

There's a bit of trickery at play, because getting an implementation to use
a project requires ensuring that project is available before functions like
update_project exist,* and I'm not comfortable enough yet with clbuild
internals to attempt rearranging things.

The patch continues the current assumption that, if a lisp bundles a copy
of ASDF, that's the preferred copy.

* I understand now why asdf is not in the projects file, and why the CVS
  invocations were hardcoded into the clbuild script itself.