From christoph.senjak at googlemail.com  Mon Mar  1 20:38:53 2010
From: christoph.senjak at googlemail.com (Christoph Senjak)
Date: Mon, 1 Mar 2010 21:38:53 +0100
Subject: [clbuild-devel] Support for Lisp-Magick
Message-ID: <33ed8ce71003011238p36a3bb4nc44c246c70325119@mail.gmail.com>

Hello.

Lisp-Magick is one (current) dependency of my project, and I noticed
that it cannot yet be installed with clbuild. Unfortunately, there
doesnt seem to be a darcs-repo or something, only a Tar-Download.

http://www.nil.at/software/lisp-magick.html

Can you add support to it?

Regards,
Christoph Senjak



From nikodemus at random-state.net  Thu Mar 11 18:57:49 2010
From: nikodemus at random-state.net (Nikodemus Siivola)
Date: Thu, 11 Mar 2010 20:57:49 +0200
Subject: [clbuild-devel] update project info for Alexandria and Hemlock
Message-ID: <633d72b1003111057n3ed5888axdee3d3bc10c53d96@mail.gmail.com>

Alexandria has moved to a git repo.

Hemlock repository url is wrong, and is missing several deps.

Also, there is no editor-hints -- ITYM named-readtables.

Cheers,

 -- Nikodemus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: project-info.diff
Type: application/octet-stream
Size: 3749 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20100311/8ad5a949/attachment.obj>

From neuss at kit.edu  Tue Mar 16 13:47:31 2010
From: neuss at kit.edu (Nicolas Neuss)
Date: Tue, 16 Mar 2010 14:47:31 +0100
Subject: [clbuild-devel] Femlisp->clbuild
Message-ID: <87mxy8v0ng.fsf@ma-patru.mathematik.uni-karlsruhe.de>

Dear clbuild-maintainers,

would you please consider adding my PDE-solver Femlisp[*] to clbuild?
This can be done very easily by adding the line

femlisp          get_cvs_full :pserver:anonymous at cvs.savannah.nongnu.org:/cvsroot/femlisp femlisp

to the file "wnpp-projects".  Since it is quite self-contained, there
are no necessary dependencies, and it should compile on a lot of CL
implementations including SBCL.

Thank you very much,
Nicolas

[*] See http://www.femlisp.org for more information.

-- 
PD Dr. Nicolas Neuss   KIT Karlsruhe   Tel: 0049-721-608-7634
Email: neuss at kit.edu   WWW:  <http://www.math.kit.edu/~neuss>



From lispercat at gmail.com  Wed Mar 17 20:04:41 2010
From: lispercat at gmail.com (Andrei Stebakov)
Date: Wed, 17 Mar 2010 16:04:41 -0400
Subject: [clbuild-devel] can't get bordeaux-threads
Message-ID: <affe56e01003171304x478c93odf075443f1bebaf7@mail.gmail.com>

cbuild complains:
NEW darcs get bordeaux-threads
Invalid repository:
http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads

darcs failed:  Failed to download URL
http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads/_darcs/inventory:
HTTP error (404?)

error: update was interrupted.

I checked
http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads/ it's
working.

Thank you,
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20100317/9162128f/attachment.html>

From lispercat at gmail.com  Thu Mar 18 22:02:31 2010
From: lispercat at gmail.com (Andrei Stebakov)
Date: Thu, 18 Mar 2010 18:02:31 -0400
Subject: [clbuild-devel] can't get bordeaux-threads
In-Reply-To: <affe56e01003171304x478c93odf075443f1bebaf7@mail.gmail.com>
References: <affe56e01003171304x478c93odf075443f1bebaf7@mail.gmail.com>
Message-ID: <affe56e01003181502q6da1f8f3x40d0db9729e3630e@mail.gmail.com>

The problem was an old darcs on my ubuntu system.
I use SBCL and it looks like
./clbuild install weblocks cl-prevalence
doesn't install trivial-backtrace.

Andrei



On Wed, Mar 17, 2010 at 4:04 PM, Andrei Stebakov <lispercat at gmail.com>wrote:

> cbuild complains:
> NEW darcs get bordeaux-threads
> Invalid repository:
> http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads
>
> darcs failed:  Failed to download URL
> http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads/_darcs/inventory: HTTP error (404?)
>
> error: update was interrupted.
>
> I checked
> http://common-lisp.net/project/bordeaux-threads/darcs/bordeaux-threads/it's working.
>
> Thank you,
> Andrew
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20100318/d4a20713/attachment.html>

From bryan.emrys at gmail.com  Sat Mar 20 19:24:00 2010
From: bryan.emrys at gmail.com (Bryan Emrys)
Date: Sat, 20 Mar 2010 12:24:00 -0700
Subject: [clbuild-devel] Dependency Addition - Hunchentoot needs
	Trivial-Backtrace
Message-ID: <eee4647d1003201224j5db4364o62946b06beae7abf@mail.gmail.com>

Minor correction to dependencies. Hunchentoot now requires trivial-backtrace

Bryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20100320/017fe97b/attachment.html>

From neuss at kit.edu  Mon Mar 22 16:12:43 2010
From: neuss at kit.edu (Nicolas Neuss)
Date: Mon, 22 Mar 2010 17:12:43 +0100
Subject: [clbuild-devel] Maintainer?
Message-ID: <877hp48hdw.fsf@ma-patru.mathematik.uni-karlsruhe.de>

Hello,

I keep seeing only mails reporting issues on this list, but no reaction
from any maintainer.  I would be interested in who is maintaining
clbuild and if (s)he is still active/alive?

Nicolas



From david at lichteblau.com  Mon Mar 22 16:30:13 2010
From: david at lichteblau.com (David Lichteblau)
Date: Mon, 22 Mar 2010 17:30:13 +0100
Subject: [clbuild-devel] Maintainer?
In-Reply-To: <877hp48hdw.fsf@ma-patru.mathematik.uni-karlsruhe.de>
References: <877hp48hdw.fsf@ma-patru.mathematik.uni-karlsruhe.de>
Message-ID: <20100322163013.GB20605@radon>

Quoting Nicolas Neuss (neuss at kit.edu):
> I keep seeing only mails reporting issues on this list, but no reaction
> from any maintainer.  I would be interested in who is maintaining
> clbuild and if (s)he is still active/alive?

I'm alive, but I don't have much time to spend on clbuild.

What that means is that I'm trying to merge patches, but I can only do
so if it's very easy for me.

"Very easy" for me are patches that are arriving as pull requests, i.e.

  1. The patch submitter records the patch using darcs

  2. Publishes his repository on any webserver

  3. Sends mail to the list, pointing to the repository, requesting
     that patches be pulled and moved over to the main repository

  4. The patch must not include changes to the 'dependencies' file,
     because that is being autogenerated in a separate step.

     (A separate patch to dependencies is fine, I can skip that.)

  5. Each patch should be self-contained, i.e. must not change two
     projects at once.

Anyone following these steps has a good chance that I'll type "darcs
pull" and try those patches.

Anything else (inline patches, lists of URLs, ...) is unlikely to get my
attention.


I know that the webpage doesn't have the full instructions and just says
something like "send a note to the list", but unfortunately that's
outdated.

d.



From tcr at freebits.de  Mon Mar 22 18:04:48 2010
From: tcr at freebits.de (Tobias C. Rittweiler)
Date: Mon, 22 Mar 2010 19:04:48 +0100
Subject: [clbuild-devel] Maintainer?
References: <877hp48hdw.fsf@ma-patru.mathematik.uni-karlsruhe.de>
	<20100322163013.GB20605@radon>
Message-ID: <87634oqlkv.fsf@freebits.de>

David Lichteblau <david at lichteblau.com> writes:

> Quoting Nicolas Neuss (neuss at kit.edu):
>> I keep seeing only mails reporting issues on this list, but no reaction
>> from any maintainer.  I would be interested in who is maintaining
>> clbuild and if (s)he is still active/alive?
>
> I'm alive, but I don't have much time to spend on clbuild.
>
> What that means is that I'm trying to merge patches, but I can only do
> so if it's very easy for me.
>
> "Very easy" for me are patches that are arriving as pull requests, i.e.
>
>   1. The patch submitter records the patch using darcs
>
>   2. Publishes his repository on any webserver
>
>   3. Sends mail to the list, pointing to the repository, requesting
>      that patches be pulled and moved over to the main repository
>
>   4. The patch must not include changes to the 'dependencies' file,
>      because that is being autogenerated in a separate step.
>
>      (A separate patch to dependencies is fine, I can skip that.)
>
>   5. Each patch should be self-contained, i.e. must not change two
>      projects at once.
>
> Anyone following these steps has a good chance that I'll type "darcs
> pull" and try those patches.
>
> Anything else (inline patches, lists of URLs, ...) is unlikely to get my
> attention.
>
>
> I know that the webpage doesn't have the full instructions and just says
> something like "send a note to the list", but unfortunately that's
> outdated.

So sounds like someone could step up and create/maintain a patch queue
for you.

  -T.