From bryan.emrys at gmail.com  Mon Jun  2 13:47:06 2008
From: bryan.emrys at gmail.com (Bryan Emrys)
Date: Mon, 2 Jun 2008 06:47:06 -0700
Subject: [clbuild-devel] Fwd: Re: [elephant-devel] Clbuild
Message-ID: <200806020647.06926.bryan.emrys@gmail.com>

Any of the maintainers reading the list?

----------  Forwarded Message  ----------

Subject: Re: [elephant-devel] Clbuild
Date: Sunday 01 June 2008
From: Ian Eslick <eslick at media.mit.edu>
To: Elephant bugs and development <elephant-devel at common-lisp.net>

Bryan,

Did we address these issues to your satisfaction for clbuild?

I just promoted a patch to our elephant-unstable branch (soon to be  
the main release) that provides a restart to create a my-config.sexp  
file.  If the user isn't warned explicitly, the consequences of a  
default my-config may be hard to track down, but this way we don't  
have to stop the build/load process until you load cl-sql or bdb  
backends.

Regards,
Ian

On May 11, 2008, at 5:22 PM, Bryan Emrys wrote:

> At one point the clbuild maintainers looked at elephant but had some  
> problems that prevented inclusion.
>
> Specifically:
>
> #  - needs sb-posix, but doesn't declare that dependency, meaning that
> #    it doesn't build even with a config file
> #  - ele-clsql loads clsql from the .asd file, not using :depends-on,
> #    which is completely unacceptable
> #    (we blacklist ele-clsql in clbuild.lisp because of that)
>
> Did anyone ever respond?
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel

_______________________________________________
elephant-devel site list
elephant-devel at common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

-------------------------------------------------------


From bryan.emrys at gmail.com  Thu Jun 12 18:04:44 2008
From: bryan.emrys at gmail.com (Bryan Emrys)
Date: Thu, 12 Jun 2008 11:04:44 -0700
Subject: [clbuild-devel] Fwd: Maintainers for Clbuild?
In-Reply-To: <20080612165236.GD22036@radon>
References: <eee4647d0806120926n382897edpf757737e124d8ad5@mail.gmail.com>
	<20080612165236.GD22036@radon>
Message-ID: <eee4647d0806121104l56d8e324uf30caf5aeffdd5f1@mail.gmail.com>

Are there any maintainers (i.e. people with commit access) reading the list?

Bryan

---------- Forwarded message ----------
From: David Lichteblau <david at lichteblau.com>
Date: Thu, Jun 12, 2008 at 9:52 AM
Subject: Re: Maintainers for Clbuild?
To: Bryan Emrys <bryan.emrys at gmail.com>


Hi,

(I'm recycling a blog comment on the subject here; feel free to forward
this to clbuild-devel, which I'm currently not subscribed to)

Quoting Bryan Emrys (bryan.emrys at gmail.com):
> What is the status on maintainers for clbuild? I'd hate to see it fade
into
> irrelevance because the current maintainers are already overloaded with
the
> rest of their lives.
>
> One of the ways I use it is to test build other peoples' libraries and
send
> off bug reports on builds. I know that is not it's original purpose, but
as

That's definitely part of its appeal.

> a non-professional programmer, maybe bug reports or documentation can be
my
> contribution to the lisp community.
>
> Please let me know if there is anything I can do to help.

There are several maintainers (if you count people with commit access as
maintainers), but I am not sure that they are all read the mailing list.

I would still add projects that I care about personally, and possibly
fix bugs in code I wrote, but don't have the time to review
more-than-trivial patches on the list.

Perhaps some of the committers would be willing to commit patches if you
asked them directly.

Keep in mind clbuild's history though: First there was Luke's
repository, which is history now. Then there were Christophe's
repository and my fork. Today there's the repository on common-lisp.net.

So clbuild users have dealt just fine with the fact that maintainers
have come and gone.

If some of the people with uncommitted patches are willing to make their
darcs repository publically available, I'm sure it wouldn't be a problem
for them to "take over" for a while.


d.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20080612/ab8d3e9f/attachment.html>

From bryan.emrys at gmail.com  Thu Jun 12 18:04:44 2008
From: bryan.emrys at gmail.com (Bryan Emrys)
Date: Thu, 12 Jun 2008 11:04:44 -0700
Subject: [clbuild-devel] Fwd: Maintainers for Clbuild?
In-Reply-To: <20080612165236.GD22036@radon>
References: <eee4647d0806120926n382897edpf757737e124d8ad5@mail.gmail.com>
	<20080612165236.GD22036@radon>
Message-ID: <eee4647d0806121104l56d8e324uf30caf5aeffdd5f1@mail.gmail.com>

Are there any maintainers (i.e. people with commit access) reading the list?

Bryan

---------- Forwarded message ----------
From: David Lichteblau <david at lichteblau.com>
Date: Thu, Jun 12, 2008 at 9:52 AM
Subject: Re: Maintainers for Clbuild?
To: Bryan Emrys <bryan.emrys at gmail.com>


Hi,

(I'm recycling a blog comment on the subject here; feel free to forward
this to clbuild-devel, which I'm currently not subscribed to)

Quoting Bryan Emrys (bryan.emrys at gmail.com):
> What is the status on maintainers for clbuild? I'd hate to see it fade
into
> irrelevance because the current maintainers are already overloaded with
the
> rest of their lives.
>
> One of the ways I use it is to test build other peoples' libraries and
send
> off bug reports on builds. I know that is not it's original purpose, but
as

That's definitely part of its appeal.

> a non-professional programmer, maybe bug reports or documentation can be
my
> contribution to the lisp community.
>
> Please let me know if there is anything I can do to help.

There are several maintainers (if you count people with commit access as
maintainers), but I am not sure that they are all read the mailing list.

I would still add projects that I care about personally, and possibly
fix bugs in code I wrote, but don't have the time to review
more-than-trivial patches on the list.

Perhaps some of the committers would be willing to commit patches if you
asked them directly.

Keep in mind clbuild's history though: First there was Luke's
repository, which is history now. Then there were Christophe's
repository and my fork. Today there's the repository on common-lisp.net.

So clbuild users have dealt just fine with the fact that maintainers
have come and gone.

If some of the people with uncommitted patches are willing to make their
darcs repository publically available, I'm sure it wouldn't be a problem
for them to "take over" for a while.


d.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20080612/ab8d3e9f/attachment-0001.html>

From krewink at inb.uni-luebeck.de  Mon Jun 30 16:33:06 2008
From: krewink at inb.uni-luebeck.de (Albert Krewinkel)
Date: Mon, 30 Jun 2008 18:33:06 +0200 (CEST)
Subject: [clbuild-devel] darcs patch: Add packages written by Gary W. King
	to wnpp.
Message-ID: <20080630163306.1BC26C004@pc42.inb.uni-luebeck.de>

Mon Jun 30 18:25:44 CEST 2008  Albert Krewinkel <krewink at inb.uni-luebeck.de>
  * Add packages written by Gary W. King to wnpp.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: add-packages-written-by-gary-w_-king-to-wnpp_.dpatch
Type: text/x-darcs-patch
Size: 21048 bytes
Desc: A darcs patch for your repository!
URL: <https://mailman.common-lisp.net/pipermail/clbuild-devel/attachments/20080630/9a3869e1/attachment.bin>