From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] virtual/term?
Date: Sat, 12 Mar 2005 11:30:19 -0500 [thread overview]
Message-ID: <20050312163019.GD20707@time.flatmonk.org> (raw)
In-Reply-To: <423263D3.4000304@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]
Donnie Berkholz wrote: [Fri Mar 11 2005, 10:36:51PM EST]
> > How about making a local USE "xterm" for xorg-x11, then adding it to
> > the default list? Then such users can USE=-xterm and they'll be all
> > set.
>
> I've already elaborated on how we provide a complete X implementation as
> upstream does. We've just taken the liberty of splitting it out into two
> separate ebuilds, one for xterm and one for everything else.
>
> A terminal emulator is not considered an optional part of a complete X
> implementation. I'm willing to deviate from that by saying any emulator
> could be acceptable rather than just xterm, but perhaps that was a bad idea.
virtual/term implies that gnome-terminal and konsole are a replacement
for xterm. That is hard to swallow since they can be more easily
broken by library snafus.
Since your goal is to provide as complete an X implementation as
upstream, I think that in order to implement virtual/term you would
also need to create an "xterm" symlink to the current terminal
emulator. That would require making the various virtual/terms
conflict with each other... probably not what anybody wants!
IMHO there are only two ways to solve this:
1. maintain the complete X distribution, PDEPEND on xterm, ignore
the whining, or
2. create some local USE flags for xorg-x11 that restrict the
binaries installed. One USE flag could control installation of
xterm, another could prevent misc programs like oclock, xeyes,
xbiff, xcalc, xedit, etc.
Choosing #1 is definitely ok, since there are Gentoo ways of solving
the problem, as one astute user mentioned in the bug report
Regards,
Aron
--
Aron Griffis
Gentoo Linux Developer
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-12 16:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 6:45 [gentoo-dev] virtual/term? Donnie Berkholz
2005-03-11 13:57 ` Mike Frysinger
2005-03-11 19:55 ` Donnie Berkholz
2005-03-11 20:39 ` Mike Frysinger
2005-03-11 22:05 ` Donnie Berkholz
2005-03-11 22:17 ` Mike Frysinger
2005-03-11 21:30 ` Andrew D. Fant
2005-03-12 0:14 ` Donnie Berkholz
2005-03-12 2:35 ` Aron Griffis
2005-03-12 2:43 ` Georgi Georgiev
2005-03-12 3:36 ` Donnie Berkholz
2005-03-12 10:45 ` Spider
2005-03-12 16:30 ` Aron Griffis [this message]
2005-03-12 17:47 ` Drake Wyrm
2005-03-12 17:56 ` Aron Griffis
2005-03-12 21:14 ` Donnie Berkholz
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=20050312163019.GD20707@time.flatmonk.org \
--to=agriffis@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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