From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 07:17:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D51D416A4DF for ; Mon, 28 Aug 2006 07:17:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 3CD6B43D46 for ; Mon, 28 Aug 2006 07:17:44 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 16065 invoked by uid 399); 28 Aug 2006 07:17:43 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 28 Aug 2006 07:17:43 -0000 Message-ID: <44F29894.9040700@FreeBSD.org> Date: Mon, 28 Aug 2006 00:17:40 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Dmitry Pryanishnikov References: <5B7BD83A-6316-4C20-903E-B5D66D4F2642@khera.org> <44EB5354.6070007@paladin.bulgarpress.com> <44EB6411.4040406@paladin.bulgarpress.com> <20060823193309.GA77890@rambler-co.ru> <44ECBFE8.7000809@FreeBSD.org> <20060824082012.GA81296@rambler-co.ru> <20060827002203.A39026@atlantis.atlantis.dp.ua> <44F130B2.8010702@FreeBSD.org> <20060827193347.J1751@atlantis.atlantis.dp.ua> In-Reply-To: <20060827193347.J1751@atlantis.atlantis.dp.ua> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: 5.5 to 6.1 upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 07:17:44 -0000 Dmitry Pryanishnikov wrote: > Hmm, let me cite your letter in this thread: This isn't a court of law. :) > sysutils/portconf does not have that limitation. If you specify flags using > that method, they will always be used. > > FYI, > > Doug > ========================================================================= > > So, one can mistakenly think that "always" here really means ALWAYS > (i.e., for every port). However many ports use that funny OPTIONS (in > the ports sense) which completely ignore make's WITH_xxx / WITHOUT_xxx > environment variables, so "always" isn't correct word here I suppose. I probably should have said, "will always work like a a variable in make.conf would." If I caused confusion, I apologize. As for the other things you mentioned, I'm sure that the respective authors would welcome patches to correct the shortcomings you perceive. Doug -- This .signature sanitized for your protection