From: Greg Troxel <gdt@ir.bbn.com>
Cc: guile-user@gnu.org
Subject: Re: guile-gtk
Date: 27 May 2004 08:41:17 -0400 [thread overview]
Message-ID: <rmin03uhwk2.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0405261922490.58417@cassandra.whitefang.com>
I made my own from CVS.
start here
http://www.gnu.org/software/guile-gtk/
or just
cvs -d anoncvs@savannah.gnu.org:/cvsroot/guile-gtk co guile-gtk
It would be really nice if a tarball of the head of the gtk 1.2 branch
of guile-gtk were created and released; it is probably better than the
latest tarball that's out there.
<rant,somewhat-joking>
I know everyone really just like to play with arch and not do
releases. But for these projects (guile-gtk and guile-gobject) to get
used by "users", it's necessary to release tarballs. I'm trying to
use guile-gtk on a project (as a tool, not trying to hack on it), and
I had to make my own tarball and then my own netbsd pkgsrc entry for
it. Not a big deal, but it's harder than using something else.
</rant,somewhat-joking>
--
Greg Troxel <gdt@ir.bbn.com>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-05-27 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 2:23 guile-gtk Thamer Al-Harbash
2004-05-27 9:57 ` guile-gtk Andreas Rottmann
2004-05-27 12:41 ` Greg Troxel [this message]
2004-05-27 14:35 ` guile-gtk Thamer Al-Harbash
2004-05-27 16:27 ` Tarballs (was guile-gtk) Mike Gran
2004-05-27 22:15 ` guile-gtk Kevin Ryde
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 20:41 guile-gnome releases: platform 2.7.96, bunch of "extras" Andy Wingo
2004-11-16 19:46 ` Neil Jerram
2004-11-16 20:10 ` Greg Troxel
2004-11-17 14:05 ` guile-gtk Bill Schottstaedt
2004-11-17 19:27 ` guile-gtk Greg Troxel
2004-11-21 17:00 ` guile-gtk 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
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=rmin03uhwk2.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--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).