From owner-freebsd-ports Mon Aug 28 15:44:58 2000 Delivered-To: freebsd-ports@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id F36C537B424; Mon, 28 Aug 2000 15:44:53 -0700 (PDT) Received: from silvia.hip.berkeley.edu (sji-ca1-02.ix.netcom.com [209.109.232.2]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id SAA22999; Mon, 28 Aug 2000 18:44:45 -0400 (EDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id PAA33088; Mon, 28 Aug 2000 15:44:41 -0700 (PDT) To: "Akinori -Aki- MUSHA" Cc: Steve Price , freebsd-ports@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: New variable suggestion: PKGNAMELANGPREFIX References: <200008270613.XAA20399@freefall.freebsd.org> <20000827105933.C268@bonsai.hiwaay.net> <863djpwbff.wl@archon.local.idaemons.org> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 28 Aug 2000 15:44:35 -0700 In-Reply-To: "Akinori -Aki- MUSHA"'s message of "Tue, 29 Aug 2000 02:19:32 +0900" Message-ID: Lines: 36 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: "Akinori -Aki- MUSHA" * This is my second try to clean up PKGNAMEPREFIX pollution. * * Here I'd suggest introducing PKGNAMELANGPREFIX to give a special * treatment to language specific prefixes. I don't like this very much. This is a generic problem, of a variable (PKGNAMEPREFIX) possibly being a concatenation of multiple elements. A generic problem should be addressed by a generic solution. Otherwise, we could run in to similar problems in the future (for instance, what if there is a port that require two non-lang-specific prefixes?) * The main reason is that the current implementation of PKGNAMEPREFIX * forces each port to know/care if the port itself or any of its slave * ports is lang-specific. This is not a problem. A porter surely will know wheter a port has slave ports that needs its own PKGNAMEPREFIX. (A master port has to be written in a certain way anyway. :) * Secondly, there is no way to judge if a PKGNAMEPREFIX is * lang-specific. Having PKGNAMELANGPREFIX separate from PKGNAMEPREFIX * would makes it easier for a cross-language master-slave port to check * what language it should be configured for. Again, same (non-)problem. By the way, if a master port wants to know which language it is dealing with, the better way would be to pass an extra variable, not overloading PKGNAMEPREFIX. That is what most master/slave ports do (RESOLUTION, PAPERSIZE, etc...). Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message