From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Andreas Rottmann Newsgroups: gmane.lisp.guile.user,gmane.lisp.guile.devel Subject: Arch and Guile Date: Mon, 01 Mar 2004 15:27:38 +0100 Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Message-ID: <87n0707icl.fsf_-_@alice.rotty.yi.org> References: <200402292232.51103.clinton@unknownlamer.org> <87r7wdma3d.fsf@alice.rotty.yi.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1078165077 2522 80.91.224.253 (1 Mar 2004 18:17:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 Mar 2004 18:17:57 +0000 (UTC) Cc: guile-user@gnu.org, guile-devel@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Mar 01 19:17:48 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Axrz9-00010m-00 for ; Mon, 01 Mar 2004 19:17:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1Axryu-0002Ra-CZ for guile-user@m.gmane.org; Mon, 01 Mar 2004 13:17:32 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AxoTJ-0006HE-8n for guile-user@gnu.org; Mon, 01 Mar 2004 09:32:41 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AxoSl-00068T-0D for guile-user@gnu.org; Mon, 01 Mar 2004 09:32:38 -0500 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.30) id 1AxoOk-0005Jk-Ou for guile-user@gnu.org; Mon, 01 Mar 2004 09:27:58 -0500 Original-Received: (qmail 17609 invoked by uid 65534); 1 Mar 2004 14:27:54 -0000 Original-Received: from chello212186006140.401.14.univie.teleweb.at (EHLO garibaldi) (212.186.6.140) by mail.gmx.net (mp010) with SMTP; 01 Mar 2004 15:27:54 +0100 X-Authenticated: #3102804 Original-Received: from ivanova.rhinosaur.lan ([192.168.1.9] helo=ivanova) by garibaldi with esmtp (Exim 4.30) id 1AxoOQ-00019d-Vs; Mon, 01 Mar 2004 15:27:38 +0100 Original-Received: from andy by ivanova with local (Exim 4.30) id 1AxoOQ-0001W5-Pd; Mon, 01 Mar 2004 15:27:38 +0100 Original-To: ttn@glug.org In-Reply-To: (Thien-Thi Nguyen's message of "Mon, 01 Mar 2004 12:10:24 +0100") User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) X-Spam-Score: -4.9 (----) X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.user:2867 gmane.lisp.guile.devel:3469 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:2867 Thien-Thi Nguyen writes: > This fork-thing is quite a f**ckup IMHO. > > it's probably better to call it a forced-inconvenience than a fork. > in any case, it has demonstrated the delicate nature of using cvs for > revision control. > Using Arch would also make stuff easier for the "mainstream" Guile developers to maintain their stable and development branches: They could have an guile--fixes--1.6 branch, wich they'd simple star-merge into HEAD. > perhaps you could ask Miles Bader how he set up the arch-cvs gateway > for emacs, and do the same for guile. > I already have a bit of experience with tla-cvs-sync from tla-tools. For running a gateway in both directions, one needs Guile CVS write access. I could set up a gateway that tracks CVS and hosts additional stuff from various sources, however. A potential problem with that is that merges into CVS (if to happen) should happen via a tool such as tla-cvs-sync and not via ordinary patches. > i would like to learn how to use such a gateway once it is available > and there are docs for the newbie (me). btw, i'm glad to host such > docs or links to them in . > Such a gateway is very simple to use: You have someone who is the "Gatekeeper" between the Arch and CVS world. This person then merges stuff form other people's branches into the dedicated "CVS" branch, which is synced with CVS in both directions. Due to the distributed nature of Arch, such a Gatekeeper could have "lieutenants", which are responsible accumulating the "good" stuff from several people into their "integration" branches. This means Gatekeeper doesn't (need to) become a bottleneck, even if there are a a lot of people contributing on the Arch side. I think that I'm not suitable as a Gatekeeper, since I'm not a Guile (core) hacker and haven't assigned copyright (yet). It would be really, really terrific if someone of the core hackers would take this responsibility. I volunteer helping with * Setting up the Gateway. If I get positive feedback, I might set up a CVS-tracking-but-not-commit gateway as described above. If the stuff in the Arch world is considered interesting enough for the Guile core hackers, one of them might want to take over Gatekeepership. Actually, this sounds like a good intermediate plan. Thoughts? * As a (first? ;-) lieutenant, leaving the Gatekeeper only with a single branch to deal with. > previously i had thought it better to wait until there is available > an implementation of the arch "wire protocol" (whatever that may be) > in guile scheme, but perhaps that is too hard line... > I'm not totally clear what you mean here, and how that relates to an Arch<->CVS gateway. Anyway, you might be interested in my ITLA thingy[0]. Cheers, Andy -- Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://mail.gnu.org/mailman/listinfo/guile-user