On 09/09/2015 07:07, Ben Woods wrote:
> On 9 September 2015 at 07:00, Piotr Kubaj wrote:
>> On 09/09/2015 06:44, Don Lewis wrote:
>>> If you list the distfiles that you want to have automatically extracted
>>> in EXTRACT_ONLY, then it will leave the unlisted ones untouched.
>> But I want the other
On 9 September 2015 at 07:00, Piotr Kubaj wrote:
> On 09/09/2015 06:44, Don Lewis wrote:
>> If you list the distfiles that you want to have automatically extracted
>> in EXTRACT_ONLY, then it will leave the unlisted ones untouched.
> But I want the other one to properly extract and compile. Does t
On 09/09/2015 06:44, Don Lewis wrote:
> If you list the distfiles that you want to have automatically extracted
> in EXTRACT_ONLY, then it will leave the unlisted ones untouched.
But I want the other one to properly extract and compile. Does that mean
I'd have to write my own extract: step?
sign
org] on
>> behalf of Piotr Kubaj [pku...@riseup.net]
>> Sent: Tuesday, September 08, 2015 4:44 PM
>> To: freebsd-ports@FreeBSD.org
>> Subject: Is there an equivalent of NO_EXTRACT?
>>
>> I'm a maintainer of a few ports. For the next update I'm preparin
eup.net]
> Sent: Tuesday, September 08, 2015 4:44 PM
> To: freebsd-ports@FreeBSD.org
> Subject: Is there an equivalent of NO_EXTRACT?
>
> I'm a maintainer of a few ports. For the next update I'm preparing, I
> want to make it possible to download some addons via options. The
Subject: Is there an equivalent of NO_EXTRACT?
I'm a maintainer of a few ports. For the next update I'm preparing, I
want to make it possible to download some addons via options. The thing
is, they are downloaded as-is. They are not meant to be extracted
(although they are zips), since it
I'm a maintainer of a few ports. For the next update I'm preparing, I
want to make it possible to download some addons via options. The thing
is, they are downloaded as-is. They are not meant to be extracted
(although they are zips), since it's the program itself that manages it.
Is there such a po
