On 3/31/14 3:47 PM, Kevin Oberman wrote:
> This is something I've wanted to have for quite a while, but never
> enough to dig through the Makefiles.
>
> I think the proper way would be for "make showconfig" to print out the
> current config as it does now, but to tag default options (e.g. '+') so
On Mon, Mar 31, 2014 at 7:47 AM, John W. O'Brien wrote:
> On 3/30/14 10:21 PM, Randy Pratt wrote:
> > On Sun, 30 Mar 2014 17:13:15 -0400
> > "John W. O'Brien" wrote:
> >
> >> [blah blah blah]
> >>
> [...]
> >> The first part of my solution to these problems is to store only the
> >> options that
On 3/30/14 10:21 PM, Randy Pratt wrote:
> On Sun, 30 Mar 2014 17:13:15 -0400
> "John W. O'Brien" wrote:
>
>> [blah blah blah]
>>
[...]
>> The first part of my solution to these problems is to store only the
>> options that I know I care about. That is, I know I need to find out
>> where a stored
On Sun, 30 Mar 2014 17:13:15 -0400
"John W. O'Brien" wrote:
> Hello ports@,
>
> In the bad old days before poudriere and various improvements to
> OptionsNG came to town, when I was using portmaster* to handle upgrades,
> I cobbled together a configuration management practice that involved
> usi
Hello ports@,
In the bad old days before poudriere and various improvements to
OptionsNG came to town, when I was using portmaster* to handle upgrades,
I cobbled together a configuration management practice that involved
using rsync and git to store /var/db/ports in a repository. The usual
workflo
