From: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-user@gnu.org
Subject: Re: guile-core in Arch archive
Date: Fri, 12 Mar 2004 10:31:25 +0100 [thread overview]
Message-ID: <87r7vyfm36.fsf@ivanova.rotty.yi.org> (raw)
In-Reply-To: 200403101734.20971.clinton@unknownlamer.org
Clinton Ebadi <clinton@unknownlamer.org> writes:
> On Saturday 06 March 2004 12:17, Andreas Rottmann wrote:
>> First, I'm happy to announce the availibility of an Arch "mirror" of
>> the Guile CVS. It's located at:
>>
>> http://people.debian.org/~rotty/arch/rotty@debian.org/guile-2004/
>>
>> In the category guile-core, there is a cvs-trunk branch, which will
>> follow CVS HEAD. I might one day start auto-building Debian packages
>> for experimental from that (and maybe other branches).
>> patch-2
>> Applied extended -e patch by Clinton Ebadi
>>
>> patch-3
>> Applied getopt-long patch by Clinton Ebadi
>
> You may want to undo the extended -e patch; I had forgotten that
> Guile CVS now reads the argument to -e and the (@ (module)
> procedure) syntax provides an easy enough way to do things. Maybe
> ttn's extended syntax could be supported with another option (-m?)
> or somehow supported by -e for compatibility with his 1.4.1.x tree
> (I don't really see how that would work, since (foo bar) could be a
> procedure call that returns the entry procedure).
>
I think I'll open an --integration branch, into which I'll cherry-pick
the features that are somewhat approved by the Guile developers. So
far, from what I've heard from Marius, getopt-long would be a good
candidate for that.
Also, I think there should be somewhat detailed ChangeLog entries for
the changes, so judging the changes is easier.
>> You might consider branching off that and I'll star-merge your changes
>> back in, which lowers effort for both off us (just make sure you
>> commit clean changesets, as you've done now).
>
> Never a better time than the present to learn how to use arch.
>
If you have any questions wrt. to using Arch/the archive, don't
hesitate to ask me (not that I'm an Arch guru yet, but at least I got
some experience).
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
Say NO to Software Patents! -- http://petition.eurolinux.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-03-12 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 1:37 Patches from ttn's tree to Guile CVS Clinton Ebadi
2004-03-06 15:57 ` Neil Jerram
2004-03-10 23:46 ` Marius Vollmer
2004-03-14 10:44 ` Andreas Rottmann
2004-03-21 2:11 ` Marius Vollmer
2004-03-06 17:17 ` guile-core in Arch archive [was: Patches from ttn's tree to Guile CVS] Andreas Rottmann
2004-03-10 22:34 ` Clinton Ebadi
2004-03-12 9:31 ` Andreas Rottmann [this message]
2004-03-10 23:32 ` Tom Lord
2004-03-07 11:04 ` Patches from ttn's tree to Guile CVS Marius Vollmer
2004-03-09 20:35 ` Marius Vollmer
2004-03-09 20:36 ` Marius Vollmer
2004-03-09 20:42 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r7vyfm36.fsf@ivanova.rotty.yi.org \
--to=a.rottmann@gmx.at \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).