--On Tuesday, June 29, 2010 09:02:35 -0500 Scot Hetzel
wrote:
On Tue, Jun 29, 2010 at 1:34 AM, Darren Pilgrim wrote:
Paul Schmehl wrote:
I'm working on a port update for one of the ports that I maintain, and
I've run into a problem that I can't seem to solve.
I use this construction to en
On Tue, Jun 29, 2010 at 1:34 AM, Darren Pilgrim wrote:
> Paul Schmehl wrote:
>>
>> I'm working on a port update for one of the ports that I maintain, and
>> I've run into a problem that I can't seem to solve.
>>
>> I use this construction to ensure that the port doesn't overwrite the conf
>> file,
On Mon, Jun 28, 2010 at 5:24 PM, Paul Schmehl wrote:
> I'm working on a port update for one of the ports that I maintain, and I've
> run into a problem that I can't seem to solve.
>
> I use this construction to ensure that the port doesn't overwrite the conf
> file, if one exists:
>
> .for f in ba
Paul Schmehl wrote:
I'm working on a port update for one of the ports that I maintain, and I've run
into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the conf
file, if one exists:
.for f in barnyard2.conf
${INSTALL_DATA} ${WR
Em 2010.06.29. 0:24, Paul Schmehl escreveu:
I'm working on a port update for one of the ports that I maintain, and
I've run into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the
conf file, if one exists:
.for f in barnyard2.conf
