<div class="gmail_quote">2008/10/22 Henrik Hjelte <span dir="ltr"><<a href="mailto:henrik@evahjelte.com">henrik@evahjelte.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br><br><div class="gmail_quote"><div class="Ih2E3d">On Wed, Oct 22, 2008 at 10:10 AM, Leslie P. Polzer <span dir="ltr"><<a href="mailto:sky@viridian-project.de" target="_blank">sky@viridian-project.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<br>
At least one revision from stable produces a non-trivial<br>
merge in unstable.<br>
<br>
That would be a good opportunity to change revision control<br>
systems.<br>
<br>
If no one objects I'd do it with Mercurial and then upload<br>
the resulting repository to Bitbucket.<br>
</blockquote></div><div><br>I would prefer that we wait with changing revision control system.<br><br>Darcs 2 has solved most of darcs problems, and the darcs<br>developers are working hard with improving the performance and<br>
with windows support.</div></div></blockquote><div><br></div><div>I've been bugging the <a href="http://cl.net">cl.net</a> admins to upgrade to darcs 2 for a couple of months now. Maybe if people here leveraged their support, they might finally do something about that upgrade.</div>
<div><br></div><div>Currently, for my own projects on <a href="http://cl.net">cl.net</a>, I have a personal installation of darcs 2 in ~/bin (with a modified ~/.profile to add this directory to PATH), and my repos are all darcs 2 format. It works fairly well, although because of some other configuration issues I can't push directly (that is, on <a href="http://cl.net">cl.net</a>, bash doesn't read ~/.bashrc on startup, so I can't alter PATH for noninteractive logins).</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div>And I am working on a possibly great new Lisp cpan killer that is <br>based on darcs 2.</div>
</div></blockquote><div><br></div><div>Or maybe your new site will solve this issue. Either way, I think darcs 2 is a viable option.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div>It will have these features:<br>
<br>Automated testing of Lisp-projects cross os and cross implementation.<br>Based on Darcs 2.<br>Support for cvs, git, mercurial and tarballs as "imports" using tailor.<br>Easy install of all lisp libraries. <br>
Easy update of lisp libraries.<br>Possibility to have several forks of the same library locally.<br><br>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.<br>
<br>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..<br><br></div></div>/Henrik Hjelte<br>
<br>_______________________________________________<br>
elephant-devel site list<br>
<a href="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</a><br>
<a href="http://common-lisp.net/mailman/listinfo/elephant-devel" target="_blank">http://common-lisp.net/mailman/listinfo/elephant-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br>Elliott Slaughter<br><br>"Any road followed precisely to its end leads precisely nowhere." - Frank Herbert<br>