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.43) id 1EIhF4-0001yx-B3 for garchives@archives.gentoo.org; Fri, 23 Sep 2005 06:41:06 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j8N6Y9St011934; Fri, 23 Sep 2005 06:34:09 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 j8N6WUj1006987 for ; Fri, 23 Sep 2005 06:32:30 GMT Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by smtp.gentoo.org with esmtp (Exim 4.43) id 1EIhCo-0007KO-6E for gentoo-dev@lists.gentoo.org; Fri, 23 Sep 2005 06:38:46 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EIhBl-0008Kj-Ny for gentoo-dev@gentoo.org; Fri, 23 Sep 2005 08:37:41 +0200 Received: from ip68-230-97-182.ph.ph.cox.net ([68.230.97.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 23 Sep 2005 08:37:41 +0200 Received: from 1i5t5.duncan by ip68-230-97-182.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 23 Sep 2005 08:37:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: Two-level USE-flag system VAR: USE="minimal" for kernel sources Date: Thu, 22 Sep 2005 23:36:27 -0700 Organization: Sometimes Message-ID: References: <431C97C4.3070406@gentoo.org> <4331D9A9.9090205@egr.msu.edu> <1127420915.23254.24.camel@login.blenning.no> <200509231019.16895.jstubbs@gentoo.org> 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-97-182.ph.ph.cox.net User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) Sender: news X-Archives-Salt: 851ea65a-664f-4d40-871e-f0abb04a6801 X-Archives-Hash: 5a2cef9f9fd4878968214028b1d50202 Jason Stubbs posted <200509231019.16895.jstubbs@gentoo.org>, excerpted below, on Fri, 23 Sep 2005 10:19:14 +0900: > On Friday 23 September 2005 05:28, Tom Fredrik Blenning Klaussen wrote: >> Now as for the USE flag system. It has actually become so big that it's >> difficult to use it effectively. I would actually suggest that a two >> level system of USE flags could be employed. Something like >> wtk/gtk (Windowing Toolkit / gtk) >> wtk/kde (Windowing Toolkit / kde) > > This is just arbitrary grouping as far as USE flags themselves go. Rather > than changing the name of the flags, why not just split the flags that are > in use.desc into categories separated by comments? > > # some category > use ... > use ... > ... > > # Windowing Toolkits > gtk ... > kde ... > > # some other category > ... The problem as I see it with comment-categories for USE flags is that it doesn't well match how USE flags (and looking up USE flag descriptions) are actually used. TFBKlaussen's proposal would make it immediately obvious from an emerge --verbose --ask (or --pretend) what category was involved. Commenting use.desc (and use.local.desc) doesn't have that advantage. Additionally, when I look up a description, it's usually by grepping use.(local.)desc, and I suppose many others work similarly. I/we don't care about all the /other descriptions, only the one we are wondering about. Putting additional information in a comment line ?? lines above the flag and description in question would /not/ be helpful. OTOH, using a category/flag arrangement would be somewhat of a description of its own, meaning the description could be shortened, and the line would be no longer than it is currently. (With 80-char screen widths, this can be an issue.) OTOH, it's obviously yet /another/ thing for portage devs to work on, and portage is /supposed/ to be in feature request freeze ATM... I like the idea, but whether the benefits of putting it on the current feature list outweigh the costs of putting it off, is something I'm not going to even pretend I want to evaluate. =8^| If you portage devs believe it's easy to "make it so", perhaps further discussion is warranted. If not, I'm not in favor of putting off the next portage yet /again/ to make it happen, tho it'd certainly be nice to have, so I'd say it's not even worth further discussion ATM. JMHO... -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-dev@gentoo.org mailing list