public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] modular X - 7.0 RC1
Date: Thu, 20 Oct 2005 11:43:21 -0700	[thread overview]
Message-ID: <4357E549.4000105@gentoo.org> (raw)
In-Reply-To: <200510201754.53322.danarmak@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Armak wrote:
| On Thursday 20 October 2005 17:28, Luca Barbato wrote:
|>a useflag could solve the issue as well a all inclusive metaebuild for X.
|
| 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.

Or, you could just activate it in the base profile.

| Also, we'd have to include RDEPEND="!noxserver? ( x11-base/xorg-x11 )" in
| every ebuild in the tree being updated to depend on
x11-base/xorg-libs. Or an
| eclass to the same effect. This would be easily forgotten in new
ebuilds, and
| then we'd get inconsistent behavior.

That's a good point. Any ideas on how to deal with it?

Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDV+VJXVaO67S1rtsRAoLsAJ0aiEOHDnpTJ/8vM5ImM23qmz1oXwCeLgG4
LVQZG0Vp/BG5IiAw5IlYc7Q=
=jMQO
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-20 18:49 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 [this message]
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
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=4357E549.4000105@gentoo.org \
    --to=spyderous@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