Hi, On Thu, Apr 14, 2005 at 19:45:22 +0200, Simone Rota wrote:
On 04/14/05 14:25 Johannes Winkelmann wrote:
Hi,
Hi,
I've just enabled the crontab job to sync per's base and opt and our contrib to the subversion repository at CLC. The repository can be browsed here: http://svn.berlios.de/viewcvs/clc/x86/tags/CRUX-2_1/
Every change in Per's CVS HEAD and ports tagged as CONTRIB-2_1 should appear there as well. Please complain if they don't (and if you care about it ;-)). Note that the sync is once per hour only.
I'm using it on my notebook and everything seems to work fine, Cool
I really hope this tests would give a spin to a possible CVS->SVN transition at CLC. (although I suspect we'd have to hypnotize Per to make him love the change) I think the transition only makes sense if we can merge between multiple architectures/platforms. From my tests with xsvn, I got the impression that this could be easily done. While I don't mean to push xsvn, I imported it into berlios' subversion repository to allow you guys to start playing with it: http://svn.berlios.de/viewcvs/clc/tools/xsvn/trunk/
In addition, I've started a page on all that, but I didn't really come to a point where I could call it finished :-) http://clc.morpheus.net:6999/clc/wiki?p=SubversionTestRepo I think a solution with subversion would be quite good for us, since it's certainly the most common OSS VCS with centralized repository; the distributed cousins all lack a way to enforce a properly merged central point to access a collection without having a dedicated patch monkey. Given our requirements, this seems pretty important to me.
That said, I plan to test importing/merging the sparc tree against this subversion tree soon, hopefully tomorrow, and will write a wiki page describing all this.
Good. I'm working on a static (binary?) svn port, as stripped as possible, as a cvsup counterpart for people who wants to avoid installing the entire svn tools and deps. Cool, that's great!
Maybe with a new binary name; I like 'svnup' even if it's already taken ( http://svnup.tigris.org/ ) I really like Jay's 'sipup' :-). I don't think the name has to be similar to cvsup. I think it would be a good idea to have a binary name different than 'svn', to allow people to break they're svn ports (e.g. by using release candidates etc) without breaking port updates. I'd even go as far as to discourage users to use this binary for other svn checkouts (even though a light client only version of subversion would be a nice addition to the ports tree). 'svup' sounds friendly to me.
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net