From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1317 invoked by uid 1002); 9 Jan 2003 22:38:30 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 13856 invoked from network); 9 Jan 2003 22:38:28 -0000 From: Paul de Vrieze To: gentoo-dev@gentoo.org Date: Thu, 9 Jan 2003 23:35:04 +0100 User-Agent: KMail/1.5 References: <20030108143105.GC1480@kruhft.dyndns.org> <200301091642.28155.gentoo-user@devrieze.net> <20030109210546.GA3312@endlessrecursion.net> In-Reply-To: <20030109210546.GA3312@endlessrecursion.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_qkfH+5Tj/vfl2nD"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200301092335.22644.gentoo-user@devrieze.net> X-Spam-Status: No, hits=-8.5 required=5.0 X-Spam-Level: X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Subject: Re: [gentoo-dev] IUSE variable clarification X-Archives-Salt: 5bf7ae6c-46e0-4829-bc95-a3557f71519d X-Archives-Hash: d83373863f4e5756bac674b2766141bd --Boundary-02=_qkfH+5Tj/vfl2nD Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Description: signed data Content-Disposition: inline On Thursday 09 January 2003 22:05, Bob Phan wrote: > > That would grab a use var right out of depend. My complaint isn't that > IUSE shouldn't exist, but that it shouldn't overlap the DEPENDs. > Redundancy like that just screams maintenence problems. I think the way > that USE variable usage inside of ebuilds is handled should be more > similar to the way that they're presented to the user. There are > multiple sources with priority to get an end list of USE variables. To > grab the list of USE vars in the ebuild it should scan DEPEND and > RDEPEND, then append IUSE to it. IUSE needn't contain anything that can > be placed in a DEPEND variable, instead it should _only_ contain USE > variables that are used, but aren't dependancies, like sse and mmx as > someone stated earlier. This should be trivial to implement in python. No DEPEND overlap is not clear either. That introduces a second place where information can be stored. Normally that is not good design. Second. I didn't talk about getting uses from DEPEND lines. Yes, that's easy. I was thinking about understanding shellscript on such a level that all invocations of use sse (where sse is an example of a DEPEND independant useflag) etc. are recognized to compose an IUSE flag. Paul ps. A validation tool that validates IUSE based on DEPEND is of course OK. pps. The use function might also be adapted to through an error if the flag is not in IUSE -- Paul de Vrieze Junior Researcher Mail: pauldv@cs.kun.nl Homepage: http://www.devrieze.net --Boundary-02=_qkfH+5Tj/vfl2nD Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+HfkqNb2zbbdIrucRAhD9AJ93T9M84XqCasRxDamES5kmR5QqcQCfQ76g FrvQOOhxgG5VAxUSgheixSM= =jqqS -----END PGP SIGNATURE----- --Boundary-02=_qkfH+5Tj/vfl2nD--