Eric Kow wrote: > ...under what > circumstances would Debian stable users need to *compile* (as > opposed to fetching a binary) *new* versions of Darcs? > For the new bit, I think it would be if we were ever to release > a version of Darcs that fixed some crucial bug (say a pending > patch issue).
What if there is a new feature or functionality that I happen to need that is still only in HEAD? That has happened in the past. It has also happened that I wanted to experiment with something. So I darcs get HEAD, compile, and hack. If my platform required some particular older tag or branch to compile, and there were some reliable easy way to find an always up-to-date source of clear instructions how to do that, I suppose that would do. It would feel unfriendly though. If the darcs team decides to disqualify everyone using Debian stable and equivalent from contributing to darcs, that of course is up to you. I personally have unfortunately not had the time to contribute so far *blushes*. The bottom line is: there are Linux users and developers (me one of them) who use Debian stable quite heavily. For us, a policy like that would work to keep our data accessible, with some small amount of inconvenience, and with a loss of some of the open-source feel of darcs. For people who have no interest to hack on darcs, keeping the data accessible with good backports is fine. Thanks, Yitz _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
