public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] XEmacs and XEmacs-gtk
@ 2003-05-09 15:04 Sergey Kuleshov
  2003-05-10  0:39 ` Matthew Kennedy
  0 siblings, 1 reply; 2+ messages in thread
From: Sergey Kuleshov @ 2003-05-09 15:04 UTC (permalink / raw
  To: gentoo-dev

Hi!
Can someone explain me, what is the reason to have xemacs and xemacs-gtk as 
two different packages? Why not add a check for gtk flag in the main xemacs 
ebuild?

Thanks

-- 
Sergey Kuleshov <sergey@til-design.com>
Let the Force be with us.

--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] XEmacs and XEmacs-gtk
  2003-05-09 15:04 [gentoo-dev] XEmacs and XEmacs-gtk Sergey Kuleshov
@ 2003-05-10  0:39 ` Matthew Kennedy
  0 siblings, 0 replies; 2+ messages in thread
From: Matthew Kennedy @ 2003-05-10  0:39 UTC (permalink / raw
  To: gentoo-dev

Sergey Kuleshov <sergey@til-design.com> writes:

> Hi!
> Can someone explain me, what is the reason to have xemacs and xemacs-gtk as 
> two different packages? Why not add a check for gtk flag in the main xemacs 
> ebuild?
>
> Thanks
>
> -- 

I can't quite remember... but I think this was a historical thing.
GTK+ support in Emacs was added to Emacs in the 21.4 series (or was
it a fork of 21.4).  Then later, support for 21.4 in general was
added to portage.  So yes, it is a bit messy, and I do agree that it
should be based on the gtk USE flag.  If you're savvy, create a patch
and post it to http://bugs.gentoo.org.

Matt
-- 
Matthew Kennedy
Gentoo Linux Developer

--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-05-10  0:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-09 15:04 [gentoo-dev] XEmacs and XEmacs-gtk Sergey Kuleshov
2003-05-10  0:39 ` Matthew Kennedy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox