Date: Thu, 28 Aug 2014 15:32:07 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: freebsd-ports@FreeBSD.org Subject: Re: auditing port options and following default option value changes Message-ID: <201408282232.s7SMW7He069463@gw.catspoiler.org> In-Reply-To: <53FECFAF.9040408@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Aug, Matthew Seaman wrote: > On 28/08/2014 04:56, Adam McDougall wrote: >> On 08/27/2014 21:12, Don Lewis wrote: >>> I'm pretty much ready to throw in the towel on upgrading ports in place >>> with portupgrade and I'm planning on switching to poudriere. As part of >>> this conversion, I'd like to figure out what ports have non-default >>> options and which options are set to non-default values. Then I can >>> figure out whether I want to set each option back to default or >>> propagate the non-default value to poudriere. >>> >>> Also, since the option files for each port contain the values for all >>> the options, if I have a port with one non-default option value set, how >>> can I follow updates to the default values of the other options? >> >> This may help: >> http://docs.freebsd.org/cgi/mid.cgi?53FDE021.5030108 That's an interesting way of handling local patches that I hadn't thought of. I just have mine scattered around the ports tree under files/ like the official patches. I can take inventory by running svn status and looking for '?'. I definitely want to switch to from individual option files to make.conf, but issue for me is trying to figure out what all should go in there from my current option files. >> I have not abandoned all my options files yet, I've eliminated some over >> time as I switch to defining options in make.conf. I'll probably get >> burned some day and finish it off. > > poudriere options creates a directory structure under > /usr/local/etc/poudriere.d/options [*] identical to what's under > /var/db/ports > so you can just make a link... > > # cd /usr/local/etc/poudriere.d > # ls -la options > lrwxr-xr-x 1 root wheel 13 Dec 24 2012 options@ -> /var/db/ports I noticed that, but I figure this is a good opportunity to clean out all the cruft that accumulated. Off the top of my head, I can think of only a small handful of things that I don't want at their default settings, and I suspect that can mostly be handled by setting them in make.conf. I just want to make sure that I'm not overlooking something in those 509 option files ... > If you also set up /usr/ports as your default ports tree: > > # poudriere ports -l > PORTSTREE METHOD TIMESTAMP PATH > default svn 2014-08-27 07:55:55 /usr/ports > > then you end up being able to ad-hoc compile anything from ports on > demand, and you can just add it to your poudriere builds after the fact. > Obviously, this is only of much use directly on your poudriere build > box, so limited to small-scale setups. I'm already doing that to handle various local patches as well as allow me to use poudriere to test build the ports that I maintain.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201408282232.s7SMW7He069463>