Re: portmaster comments

2011-03-16 Thread Andriy Gapon
on 14/03/2011 02:45 Doug Barton said the following: > BTW, the reason I'm not amenable to your suggestion in 2 is that only a few > developer-types actually care about this, and that doesn't justify the code > complexity. Just be thankful I didn't go with my first instinct, which was to > 'rm > -r

Re: portmaster comments

2011-03-14 Thread Wesley Shields
On Mon, Mar 14, 2011 at 05:08:26AM -0400, J. Hellenthal wrote: > > On Sun, 13 Mar 2011 20:45, dougb@ wrote: > > On 3/13/2011 5:35 PM, Peter Jeremy wrote: > >> Hi Doug, > >> > >> I'd like to raise a couple of nits with portmaster (primarily a wish > >> for more configurability): > >> > >> 1) In v

Re: portmaster comments

2011-03-14 Thread Matthias Andree
Am 14.03.2011 01:45, schrieb Doug Barton: On 3/13/2011 5:35 PM, Peter Jeremy wrote: Hi Doug, I'd like to raise a couple of nits with portmaster (primarily a wish for more configurability): 1) In v3.0, you added code to nice(1) all make(1) invocations. In some cases, the default niceness does n

Re: portmaster comments

2011-03-14 Thread J. Hellenthal
On Sun, 13 Mar 2011 20:45, dougb@ wrote: On 3/13/2011 5:35 PM, Peter Jeremy wrote: Hi Doug, I'd like to raise a couple of nits with portmaster (primarily a wish for more configurability): 1) In v3.0, you added code to nice(1) all make(1) invocations. In some cases, the default niceness does

Re: portmaster comments

2011-03-13 Thread Doug Barton
On 3/13/2011 5:35 PM, Peter Jeremy wrote: Hi Doug, I'd like to raise a couple of nits with portmaster (primarily a wish for more configurability): 1) In v3.0, you added code to nice(1) all make(1) invocations. In some cases, the default niceness does not suit me (in particular, I'd often prefe