From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.3/8.13.3) with ESMTP id j2L8umXf014533 for ; Mon, 21 Mar 2005 08:56:48 GMT Received: from smarthost160.mail.easynet.fr ([212.180.1.160] helo=corwin.easynet.fr) by smtp.gentoo.org with esmtp (Exim 4.43) id 1DDIiN-0003AO-Gp for gentoo-dev@robin.gentoo.org; Mon, 21 Mar 2005 08:56:47 +0000 Received: from easyconnect2121138-64.clients.easynet.fr ([212.11.38.64] helo=eusebe) by corwin.easynet.fr with esmtp (Exim 4.34) id 1DDIiJ-00035Y-PM for gentoo-dev@gentoo.org; Mon, 21 Mar 2005 09:56:44 +0100 Date: Mon, 21 Mar 2005 09:56:01 +0100 From: Thomas de Grenier de Latour To: gentoo-dev@robin.gentoo.org Subject: Re: [gentoo-dev] USE Flags Message-ID: <20050321095601.4b2c7746@eusebe> In-Reply-To: <20050321061128.6b7f0b64@sven.genone.homeip.net> References: <422EEE5D.2040702@gmx.at> <20050309140028.67bf4c1c@sven.genone.homeip.net> <200503202201.26459.pauldv@gentoo.org> <20050320232139.7eea3df7@eusebe> <20050321061128.6b7f0b64@sven.genone.homeip.net> Organization: Fasmz X-Mailer: Sylpheed-Claws 1.0.0cvs21.1 (GTK+ 2.6.4; i686-pc-linux-gnu) 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@gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 811f7ed6-e551-4133-af04-3ea1e18ba8d3 X-Archives-Hash: d0ed67843c5416db4b0ff881b3c7c9ed On Mon, 21 Mar 2005 06:11:28 +0100 Marius Mauch wrote: > (no tool support for either solution) Well, actually i've put some bits of code in the bugreport I've mentioned above, so there is tool support for the use.local.desc solution (equery and emerge). That was more to demonstrate how easy it was to implement tho, and i agree it's not the only point of the discussion. > use.local.desc for package-specific short descriptions (like at > the moment) and metadata.xml for longer detailed descriptions > if required That sounds like a good idea. So, to summarize (just to check i've understood your proposal): - users should know when a flag is really a must-have for a given package, or is at the contrary not advised, things like that. That kind of quick hints, warnings, and other answers to obvious questions like "Is DVD support by mplayer better with the 'dvdread' flag?" only require short notes (one sentence) in general. But what is important is that they get written whenever there is something to say about a flag which is not already in use.desc (because package-specific), and that they are easily accessible for the user. Here, use.local.desc seems better, because there is no such thing as an "echo >>" to drop a quick note somewhere, and because it doesn't require complex code or access to multiple files to get optionaly displayed by emerge in pretend mode. - user might sometimes wonder what is the "libfoo" that the "foo" flag description ("add support for libfoo") talks about. That may require a long description (one paragraphe), which don't need to be in use.local.desc. Metadata.xml is fine here, since anyway that's the kind of things you write using a text editor. That raises on more question tho: if someone wants to write a long description for a global flag, where does he do it? -- TGL. -- gentoo-dev@gentoo.org mailing list