On Oct 3, 2013, at 2:52 PM, Peter Danecek wrote:
> On Oct 3, 2013, at 20:40 , Joshua Root wrote:
>
>> On 2013-10-4 04:07 , Peter Danecek wrote:
>>>
>>> Hi all,
>>>
>>> one more question (at least) related to subports.
>>>
>>> In my Portfile w/ subports I use variants, which allow to switch
On Oct 3, 2013, at 20:40 , Joshua Root wrote:
> On 2013-10-4 04:07 , Peter Danecek wrote:
>>
>> Hi all,
>>
>> one more question (at least) related to subports.
>>
>> In my Portfile w/ subports I use variants, which allow to switch features.
>> These would apply to basically to all subports
On 2013-10-4 04:07 , Peter Danecek wrote:
>
> Hi all,
>
> one more question (at least) related to subports.
>
> In my Portfile w/ subports I use variants, which allow to switch features.
> These would apply to basically to all subports so I put them global. But
> there would be one exception,
On 2013-10-03 20:35, Ryan Schmidt wrote:
> if {${subport} ne "irods-doc"} {
> variant unicore {
>
> }
> }
Ah, right, I keep forgetting about "eq" and "ne"...
This is the better, correct way to compare the strings.
Rainer
___
macport
On 2013-10-03 20:07, Peter Danecek wrote:
> I did not really expect it would work, but I am looking for something like
> this:
>
> subport irods-doc {
> variant-delete unicore
> }
This is not possible with a declarative syntax, but can be achieved
imperatively:
if {$subport != "irods-doc"}
On Oct 3, 2013, at 13:07, Peter Danecek wrote:
> In my Portfile w/ subports I use variants, which allow to switch features.
> These would apply to basically to all subports so I put them global. But
> there would be one exception, these variants make no sense for
> documentations, so ideally I
Hi all,
one more question (at least) related to subports.
In my Portfile w/ subports I use variants, which allow to switch features.
These would apply to basically to all subports so I put them global. But there
would be one exception, these variants make no sense for documentations, so
idea
