Date: Sat, 01 Jan 2011 11:18:02 -0800 From: Doug Barton <dougb@FreeBSD.org> To: bf1783@gmail.com Cc: "b. f." <bf1783@googlemail.com>, freebsd-ports@FreeBSD.org Subject: Re: ports-mgmt/portconf , ports-mgmt/portmaster and make args Message-ID: <4D1F7DEA.9020006@FreeBSD.org> In-Reply-To: <AANLkTimCd6tRqPWHj%2BTOWTmB8rM7uVq%2BQVeYdcZz2VJc@mail.gmail.com> References: <AANLkTimCd6tRqPWHj%2BTOWTmB8rM7uVq%2BQVeYdcZz2VJc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/31/2010 18:40, b. f. wrote: > You don't need to go to those lengths. You could just add a > command-line switch, or a check for a cookie (.buildme or .nopkg, say) > in the corresponding PORT_DBDIR subdirector(y|ies), or both, to allow > the user to indicate to portmaster that it should always build the > port(s) in question, even if -P is used. My preferences are for something that it's possible for other port tool authors to use, and something that requires the minimal necessary steps for the user. Since the OP is already editing knobs in ports.conf, and since IMO either ports.conf or make.conf are easier to transport between systems I think I'll give Matthew's idea a try first. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D1F7DEA.9020006>