On 04/21/2011 11:05 AM, Nigel Kersten wrote:
> On Thu, Apr 21, 2011 at 11:03 AM, Russell Jackson wrote:
>
>> The ports provider doesn't work due to bugs in portupgrade when run
>> without a controlling tty. I opened a problem report about this sometime
>> ago and recommended removing the provider
On Thu, Apr 21, 2011 at 11:03 AM, Russell Jackson wrote:
> The ports provider doesn't work due to bugs in portupgrade when run
> without a controlling tty. I opened a problem report about this sometime
> ago and recommended removing the provider entirely.
I'll chase this up now Russell.
> The p
On 04/20/2011 02:45 PM, Nigel Kersten wrote:
> On Fri, Apr 15, 2011 at 3:26 PM, fafaforza wrote:
>> New user trying to get a port to compile: I tried searching but all I
>> get are links to the FreeBSD port of puppet. Easier to find a needle
>> in a haystack.
>>
>> A class has:
>>
>> exec { "por
On Fri, Apr 15, 2011 at 3:26 PM, fafaforza wrote:
> New user trying to get a port to compile: I tried searching but all I
> get are links to the FreeBSD port of puppet. Easier to find a needle
> in a haystack.
>
> A class has:
>
> exec { "port-sudo":
> cwd => "/usr/ports/security/
On 04/16/2011 12:26 AM, fafaforza wrote:
> New user trying to get a port to compile: I tried searching but all I
> get are links to the FreeBSD port of puppet. Easier to find a needle
> in a haystack.
>
> A class has:
>
> exec { "port-sudo":
> cwd => "/usr/ports/security/sudo",
New user trying to get a port to compile: I tried searching but all I
get are links to the FreeBSD port of puppet. Easier to find a needle
in a haystack.
A class has:
exec { "port-sudo":
cwd => "/usr/ports/security/sudo",
environment => "BATCH=yes",
command =
