From: Andy Wingo <wingo@pobox.com>
To: guile-gtk@sources.redhat.com
Subject: Re: The GTK2 line of development
Date: Mon, 02 Jun 2003 06:51:00 -0000 [thread overview]
Message-ID: <20030526174448.GC6014@lark> (raw)
In-Reply-To: <20030524000841.30f8d5df.stan@altosw.be>
On Sat, 24 May 2003, Stan Pinte wrote:
> On Sat, 24 May 2003 12:41:11 +0100
> Andy Wingo <wingo@pobox.com> wrote:
>
> > - within savannah.nongnu.org
> > * has the advantage that all guile-gtk stuff is in the same place
> > (maybe it's an advantage, who knows)
>
> I would favor that option, as I just moved the (gnome guile) code from
> the Gnome CVS to the savannah Guile-gtk project. (All the (gnome guile)
> code is in a separate module, under
> http://savannah.nongnu.org/cgi-bin/viewcvs/guile-gtk/gnome-guile-0.1/
Sounds reasonable. The developers on this codebase will probably be
mainly guile hackers rather than gnome hackers, so that seems about
right. Then we just have to figure out package names and module names.
The gtk-1.2 code uses the module name (gtk gtk), if I'm not mistaken.
See the previous email for my thoughts on namespaces -- there's no
collision here, in my eyes. The guile-gnome code that was in
gnome-guile-0.10 (I am getting confused now) uses the module (gnome
gnome). Hmm...
I guess ideally(tm) I would like the (gnome ...) namespace to be
reserved for the 2.x version. That does conflict with the current naming
of your project, does it not? Still, if you continue to use (gnome
guile) and submodules, there shouldn't be any problems.
The win-win situation would be to coerce you to join 2.x development,
hehehe ;-)
Do I have a correct summary of the situation?
regards,
wingo.
next prev parent reply other threads:[~2003-06-02 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 12:04 Andy Wingo
2003-05-24 14:08 ` Stan Pinte
2003-06-02 6:51 ` Andy Wingo [this message]
2003-06-02 10:06 ` Stan Pinte
2003-05-25 23:31 ` Kevin Ryde
2003-06-02 6:51 ` Andy Wingo
2003-06-02 12:05 ` Dale P. Smith
2003-06-02 13:04 ` Andy Wingo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030526174448.GC6014@lark \
--to=wingo@pobox.com \
--cc=guile-gtk@sources.redhat.com \
/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).