From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1ESfzA-0000CQ-8A for garchives@archives.gentoo.org; Thu, 20 Oct 2005 19:21:56 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j9KJIcZE011342; Thu, 20 Oct 2005 19:18:38 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j9KJEvtw015092 for ; Thu, 20 Oct 2005 19:14:57 GMT Received: from c-67-171-150-177.hsd1.or.comcast.net ([67.171.150.177] helo=[192.168.1.106]) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1ESfuu-0000P4-O7 for gentoo-dev@lists.gentoo.org; Thu, 20 Oct 2005 19:17:33 +0000 Message-ID: <4357ED4D.1040809@gentoo.org> Date: Thu, 20 Oct 2005 12:17:33 -0700 From: Donnie Berkholz User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050821) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] modular X - 7.0 RC1 References: <4357432E.2020009@gentoo.org> <200510201526.47620.danarmak@gentoo.org> <4357E3E1.4070307@gentoo.org> <200510202108.33776.danarmak@gentoo.org> In-Reply-To: <200510202108.33776.danarmak@gentoo.org> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: e58e409f-ac3b-4f62-ac03-33e0ef20bd9d X-Archives-Hash: 60a41581eb29da0797a123e3b00dcf07 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Armak wrote: | On Thursday 20 October 2005 20:37, Donnie Berkholz wrote: | |>I'd prefer that people don't come to depend on metabuilds at all. | | OK, we can do this. | | |>See |>http://dev.gentoo.org/~spyderous/xorg-x11/porting_to_modular_x_howto.txt. | | That file says there won't be any x11-related virtuals anymore. Are you sure | no package uses it in the sense of 'any X server' instead of 'any X client | libs+headers'? I'm not aware of any. The only similar thing I'm aware of is a few incredibly broken packages that require Xvfb at build time. If there are packages that need to run any X server at build time, they're even more broken. | Firstly, as I said in my other replies, this would change the current meaning | of the X USE flag. The original meaning would stay without a flag. | | Today it means 'enable support for clienside X11'. You want to make it mean | 'install X11 server'. If I'm building a headless box without an X11 server, | but I do want to emerge KDE and run it over ssh -Y from another box, I need | two useflags to specify this. But even if we introduce a new USE flag | 'Xserver', on by default where X is on by default, and used as you describe | above, the problems I describe below will remain. Does it really mean that? How about all of the X USE flags in font ebuilds? They mean basically what I'm saying. | Secondly, there can be more than one X11 server (kdrive, etc). Depending on | xorg-server is bad. If anything, we should introduce a virtual/x11-server. | | Thirdly, it's a 'convenience dep': whether xorg-server is installed or not | won't affect the behavior of KDE in any way (given a working DISPLAY | setting). Right, the intent is to basically say "I'm part of the 90% of users who has X installed locally and wants things to just work." | Finally, it requires that extra change to (ideally) all X11 client apps. It's | not intuitive, and so easy to forget when writing new ebuilds. Yeah. |>We will still install some fonts, but not all, and I'll note that in the |>metabuilds text. | | Which ones? Selected how? I'm asking because I don't want to work too hard on | deciding which fonts KDE should depend on :-) Selected arbitrarily by the x11 team based on requirement, common use and prettiness factor. Probably font-misc-misc, font-bh-ttf, font-adobe-utopia-type1 and maybe some others that are brought to my attention. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDV+1NXVaO67S1rtsRAlmXAJ4zr0ZCvF29BZwmDv/n/iagMMkIpgCgyO2h lckxp/jpUG4FZxr0PQQAyjQ= =x7RY -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list