public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] modular X - 7.0 RC1
Date: Thu, 20 Oct 2005 21:48:38 +0200	[thread overview]
Message-ID: <52ZKB4.136721026EZE64L@gentoo.org> (raw)
In-Reply-To: 200510202116.47326.danarmak@gentoo.org

On 20/10/2005 21:16:47, Dan Armak (danarmak@gentoo.org) wrote:
> On Thursday 20 October 2005 20:58, Matthijs van der Vleuten wrote:
> > On 10/20/05, Dan Armak <danarmak@gentoo.org> wrote:
> > > To solve this issue it would have to be an on-by-default flag, i.e.
> > > 'noxserver'. I know some people are strongly against nofoo flags.
> >
> > What about an off-by-default 'xserver' flag?
> It wouldn't solve the problem at hand. 
> 
> Without any flag at all, the user needs to 'emerge xorg-x11' manually to 
> get eg KDE to run locally. With an off-by-default flag, he needs to set 
> it on manually, _before_ installing KDE, to get an xorg-x11 server. As 
> long as he needs to do something manually, explicitly, it should just be 
> an 'emerge xorg-x11', which after all is a very simple operation.

Maybe I'm being stupid, but I don't understand why a user would need to
emerge xorg-x11 manually when doing 'emerge kde'.  Surely somewhere in kde's
dependency graph the X server is called up in RDEPEND?  An X server
is clearly a run-time dependency.

Like, konqueror RDEPENDS on qt which RDEPENDS on xorg-xserver, or whatever.

Kev.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-20 19:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20  7:11 [gentoo-dev] modular X - 7.0 RC1 Donnie Berkholz
2005-10-20  8:37 ` Simon Strandman
2005-10-20 12:55   ` [gentoo-dev] " Duncan
2005-10-20 12:37 ` [gentoo-dev] " Spider (D.m.D. Lj.)
2005-10-20 13:26 ` Dan Armak
2005-10-20 14:41   ` Olivier Crête
2005-10-20 15:23   ` Mike Williams
2005-10-20 15:49     ` Dan Armak
2005-10-20 15:28   ` Luca Barbato
2005-10-20 15:54     ` Dan Armak
2005-10-20 18:43       ` Donnie Berkholz
2005-10-20 19:25         ` Dan Armak
2005-10-20 19:31           ` Donnie Berkholz
2005-10-20 19:35           ` Diego 'Flameeyes' Pettenò
2005-10-20 19:35             ` Ciaran McCreesh
2005-10-20 19:42             ` Donnie Berkholz
2005-10-20 19:57               ` Mike Frysinger
2005-10-20 20:01               ` Diego 'Flameeyes' Pettenò
2005-10-20 20:13                 ` Mike Owen
2005-10-20 20:19                 ` Donnie Berkholz
2005-10-20 21:40             ` Carsten Lohrke
2005-10-20 22:17               ` Alec Warner
2005-10-20 18:58       ` Matthijs van der Vleuten
2005-10-20 19:16         ` Dan Armak
2005-10-20 19:48           ` Kevin F. Quinn [this message]
2005-10-20 19:54             ` Dan Armak
2005-10-20 21:24               ` Alec Joseph Warner
2005-10-20 21:08             ` Chris Gianelloni
2005-10-20 19:49           ` Kevin F. Quinn
2005-10-20 18:37   ` Donnie Berkholz
2005-10-20 19:08     ` Dan Armak
2005-10-20 19:17       ` Donnie Berkholz
2005-10-20 19:44         ` Dan Armak
2005-10-20 20:22           ` Donnie Berkholz
2005-10-20 21:06         ` Chris Gianelloni
2005-10-20 21:14           ` Dan Armak
2005-10-20 21:37           ` Donnie Berkholz
2005-10-20 14:46 ` Ben Skeggs
2005-10-20 15:28   ` Herbie Hopkins
2005-10-20 15:55     ` Ben Skeggs
2005-10-20 15:58 ` Dan Armak
2005-10-20 18:39   ` Donnie Berkholz
2005-10-23  4:04 ` [gentoo-dev] " R Hill

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=52ZKB4.136721026EZE64L@gentoo.org \
    --to=kevquinn@gentoo.org \
    --cc=gentoo-dev@lists.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