On 07/02/2011 21:13, Dan Langille wrote:
>
> On Mon, February 7, 2011 11:06 am, Dominic Fandrey wrote:
>> On 07/02/2011 03:01, b. f. wrote:
Over the weekend, a new feature was added to FreshPorts BETA. A port
now lists all ports that require it. This code will eventually move to
p
On Feb 07, 2011, at 14:13 , Dan Langille wrote:
> I am tempted to alter FreshPorts and abandon all *_DEPENDS and use just
> run-depends-list and build-depends-list.
>
> How much value is there is having all of this information separated into
> individual _DEPENDS?
It's critical for things like t
On Mon, February 7, 2011 11:06 am, Dominic Fandrey wrote:
> On 07/02/2011 03:01, b. f. wrote:
>>> Over the weekend, a new feature was added to FreshPorts BETA. A port
>>> now lists all ports that require it. This code will eventually move to
>>> production after it's been running on on the beta
On 07/02/2011 03:01, b. f. wrote:
>> Over the weekend, a new feature was added to FreshPorts BETA. A port
>> now lists all ports that require it. This code will eventually move to
>> production after it's been running on on the beta site for a while.
>>
>> Notes:
>>
>> * The code uses the output
On 2/6/2011 9:50 PM, b. f. wrote:
On 2/6/11, Dan Langille wrote:
On 2/6/2011 9:03 PM, b. f. wrote:
On 2/6/11, b. f. wrote:
While we're here... is there anything special about PATCH_DEPENDS,
FETCH_DEPENDS, and EXTRACT_DEPENDS that might be different than the
depends I'm already processing
On 2/6/11, Dan Langille wrote:
> On 2/6/2011 9:03 PM, b. f. wrote:
>> On 2/6/11, b. f. wrote:
>
> While we're here... is there anything special about PATCH_DEPENDS,
> FETCH_DEPENDS, and EXTRACT_DEPENDS that might be different than the
> depends I'm already processing? They seem to be the same f
On 2/6/2011 9:03 PM, b. f. wrote:
On 2/6/11, b. f. wrote:
Over the weekend, a new feature was added to FreshPorts BETA. A port
now lists all ports that require it. This code will eventually move to
production after it's been running on on the beta site for a while.
Notes:
* The code uses th
On 2/6/11, b. f. wrote:
>> Over the weekend, a new feature was added to FreshPorts BETA. A port
>> now lists all ports that require it. This code will eventually move to
>> production after it's been running on on the beta site for a while.
>>
>> Notes:
>>
>> * The code uses the output of make -
On 2/6/2011 9:01 PM, b. f. wrote:
Over the weekend, a new feature was added to FreshPorts BETA. A port
now lists all ports that require it. This code will eventually move to
production after it's been running on on the beta site for a while.
Notes:
* The code uses the output of make -V RUN_DE
> Over the weekend, a new feature was added to FreshPorts BETA. A port
> now lists all ports that require it. This code will eventually move to
> production after it's been running on on the beta site for a while.
>
> Notes:
>
> * The code uses the output of make -V RUN_DEPENDS -V LIB_DEPENDS -V
Over the weekend, a new feature was added to FreshPorts BETA. A port
now lists all ports that require it. This code will eventually move to
production after it's been running on on the beta site for a while.
Notes:
* The code uses the output of make -V RUN_DEPENDS -V LIB_DEPENDS -V
BUILD_DE
11 matches
Mail list logo