On Wed, Oct 22, 2008 at 10:10 AM, Leslie P. Polzer
<[EMAIL PROTECTED]>wrote:
>
> At least one revision from stable produces a non-trivial
> merge in unstable.
>
> That would be a good opportunity to change revision control
> systems.
>
> If no one objects I'd do it with Mercurial and then upload
> the resulting repository to Bitbucket.
>
I would prefer that we wait with changing revision control system.
Darcs 2 has solved most of darcs problems, and the darcs
developers are working hard with improving the performance and
with windows support. For example, there is an upcoming darcs
hacking sprint in three locations in a week or so.
And I am working on a possibly great new Lisp cpan killer that is
based on darcs 2. It will have these features:
Automated testing of Lisp-projects cross os and cross implementation.
Based on Darcs 2.
Support for cvs, git, mercurial and tarballs as "imports" using tailor.
Easy install of all lisp libraries.
Easy update of lisp libraries.
Possibility to have several forks of the same library locally.
You can generate one file ("project-state") that describes the exact patches
that a project uses, including dependencies. This file can be used as a
"last known good" file, so if a patch to project B breaks project A
(detected by automated testing), you can still install Project A. It is just
that the last patch to Project B will not be used for project A. But you can
still upgrade your local Project B to the latest version.
I am almost finished for a first release, but I am only hacking on it for
max 40 mins each day (on the bus). So you can call it vapourware for a
while..
/Henrik Hjelte
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
