From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: role of guile-lib
Date: Tue, 06 Jan 2009 10:27:04 +0100 [thread overview]
Message-ID: <m3mye4rdhz.fsf@pobox.com> (raw)
In-Reply-To: <87vdstbgi5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 05 Jan 2009 22:16:34 +0100")
Hi,
On Mon 05 Jan 2009 22:16, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> * Include (parts of?) [guile-lib] within Guile itself
>>
>> * Make [guile-lib] a part of Guile, but not a part of the guile source
>> distribution.
>
> Another solution: move the code to Git at Savannah (but as a project of
> its own) and provide the interested parties with commit access (I'd be
> one of these ;-)).
So, sounds like the current situation with git instead of bzr, and
hosted on savannah.
> Guile-Lib could indeed point its users to `guile-user@gnu.org'.
Yes this should be the solution in any case -- fragmenting fora for
Guile discussion is not in our interest.
Maybe your solution is best -- it lets us keep guile-lib's unit tests
and documentation system intact, doesn't bind us quite to the quality
standards of guile, but still gives us the advantages of the
git/savannah switch.
> (Practically, you'd be the one in the best position to do this, but
> then you'd be almost freed, Andy!) Then have somebody arrange to make
> releases periodically and voilà! :-)
OK, ok, ok... ;-)
So I'll see about doing this this afternoon, if everything works out.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-01-06 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 21:14 role of guile-lib Julian Graham
2008-12-25 11:23 ` Andy Wingo
2008-12-25 13:48 ` dsmich
2008-12-25 21:08 ` Julian Graham
2008-12-26 11:50 ` Neil Jerram
2009-01-05 21:11 ` Ludovic Courtès
2009-01-05 21:16 ` Ludovic Courtès
2009-01-06 9:27 ` Andy Wingo [this message]
2009-01-06 15:14 ` Ludovic Courtès
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=m3mye4rdhz.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).