From: Matthew Kennedy <mbkennedy@austin.rr.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] need advice on ebuilding xemacs 21.4.6 --with-gtk --with-gnome
Date: 07 Feb 2002 01:55:53 -0600 [thread overview]
Message-ID: <1013068554.16446.27.camel@gentoo.shacknet.nu> (raw)
As you might already know, there is an
app-editors/gtk-xemacs/gtk-xemacs-21.1.12_p3. I think this is the
original proof of concept xemacs with support for gtk and gnome. I
believe the main development for gtk-xemacs now happens in the xemacs
"gamma" branch (21.4.x) now. We already have a
app-editors/xemacs/xemacs-21.4.5.ebuild though and this is the source of
my dilemma.
The existing app-editors/xemacs/xemacs-21.4.5 will use motif (or athena
optionally) via USE. I would have liked to change
app-editors/xemacs/xemacs-21.4.x to configure --with-gtk --with-gnome,
but that is unreasonable given that people would still like to
--with-widgets=motif etc. Put another way, I can't really test USE for
gtk and gnome accordingly because poeple could have motif in there.
I had thought briefly about determining what to use to build
xemacs-21.4.x based on whether gtk and gnome appear before motif in USE,
but I haven't seen any evidence yet that USE should be used this way.
My conclusion is that gtk-xemacs-21.1.12_p3 should be superseded by a
xemacs-21.4.x --with-gnome --with-gtk (which i'm testing now on my own
machine for 21.4.6 and plan to submit to bugs.gentoo.org). I would call
the package, app-editors/gtk-xemacs/gtk-xemacs-21.4.6.ebuild and it
would be distinct from app-editors/xemacs/xemacs-21.4.x.ebuild (which
would remain motif/athena builds). Does this plan sound about right to
the more experienced contributors and maintainers?
Just checking...
Matt (irc burnside)
next reply other threads:[~2002-02-07 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 7:55 Matthew Kennedy [this message]
2002-02-07 17:23 ` [gentoo-dev] need advice on ebuilding xemacs 21.4.6 --with-gtk --with-gnome Geert Bevin
2002-02-08 0:20 ` Matthew Kennedy
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=1013068554.16446.27.camel@gentoo.shacknet.nu \
--to=mbkennedy@austin.rr.com \
--cc=gentoo-dev@gentoo.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