From: Ariel Rios <ariel@linuxppc.org>
To: Seth Alves <alves@hungry.com>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: suggestions for Guile wrt GTK and Gnome support
Date: Mon, 23 Jul 2001 22:14:00 -0000 [thread overview]
Message-ID: <995948183.1475.22.camel@soleil> (raw)
In-Reply-To: <200107231740.KAA10213@twinge.hungry.com>
On 23 Jul 2001 10:40:34 -0700, Seth Alves wrote:
> I would be very very surprised if gtk ever began to depend on gnome.
Yes indeed. That will never happen =)
> There is a module called gnome-guile in the gnome/gtk cvs tree. It
> contains the guile-gtk code, and other code that wraps the more stable
> parts of gnome. To build this from cvs, you DO need bits of the gnome
> build environment, but these dependencies are simply a convenience for
> the maintainer. Perhaps we could try to convince Ariel to break or
> reduce these dependencies?
A solution might be to fork guile-gtk in stable (1.2) and unstbale (2.0)
Strable branch should include the old autoconf stuff and the unstable
branch might use pkg-config...
>=) These dependencies only exist if you
> are building gnome-guile from cvs. If you are building with a tar.gz
> style release, you don't need any of gnome. I like gnome-guile. It
> needs some polishing in places, but overall it's very effective.
What kind of polishing?
ariel
next parent reply other threads:[~2001-07-23 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107231740.KAA10213@twinge.hungry.com>
2001-07-23 22:14 ` Ariel Rios [this message]
2001-07-23 22:50 ` Seth Alves
2001-07-26 1:59 ` Thien-Thi Nguyen
[not found] <15196.20913.8186.886002@winona.neilvandyke.org>
2001-07-23 22:12 ` Ariel Rios
2001-07-23 23:34 ` Martin Grabmueller
2001-07-24 2:37 ` Thien-Thi Nguyen
2001-07-24 5:51 ` Neil W. Van Dyke
2001-07-24 8:26 ` John Kodis
2001-07-24 6:29 ` Dale P. Smith
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=995948183.1475.22.camel@soleil \
--to=ariel@linuxppc.org \
--cc=alves@hungry.com \
--cc=guile-gtk@sourceware.cygnus.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).