Hi Jeremy and others,
I think a few lines can be simplified in the new Fortran recipe. For
default variants, it seems to me that it makes no difference whether it is
set when the variant was explicitly selected.
i.e this code from the Portfile recipe
if {![variant_isset q8] && ![variant_isset q3
Hi all,
As we see at https://trac.macports.org/wiki/PortfileRecipes, the
recommended code for a default variant with one of several mutually
exclusive variants is:
if {![variant_isset q8] && ![variant_isset q32]} {
default_variants +q16
}
In this case, as in the older Fortran recipe also on
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
Hi all,
thank you very much for the help and comments to my questions. I have a worked
version of the port now and decided the easiest way to ask you for further
review would be to submit it. It's ticket #40664.
I am aware that it cannot be committed yet, also because several dependencies
(w
On Oct 3, 2013, at 20:27 , Peter Danecek wrote:
> I reply to this on my own!
>
> On Oct 3, 2013, at 20:22 , Peter Danecek wrote:
>
>>
>> Okay, I hope that's it then with variants.
>>
>> I have one variant (+gsi for GSI authentication) I do not want to make
>> default. However, if this is
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 Oct 3, 2013, at 13:22, Peter Danecek wrote:
> I have one variant (+gsi for GSI authentication) I do not want to make
> default. However, if this is activated, I would like to an other variant to
> come with it, ( i.e. +ca-bundle, a bundle with CA certificates), so that the
> user would get
That is why my test did not work ;-)
I fixed that and it seems okay! (I send a second mail on this, but there seems
to be some delay)
~petr
On Oct 3, 2013, at 20:42 , Joshua Root wrote:
> if {[variant_isset gsi]} {
> default_variants +ca-bundle
> }
>
> BTW, "ca-bundle" is not a valid v
On 2013-10-4 04:22 , Peter Danecek wrote:
>
> Okay, I hope that's it then with variants.
>
> I have one variant (+gsi for GSI authentication) I do not want to make
> default. However, if this is activated, I would like to an other variant to
> come with it, ( i.e. +ca-bundle, a bundle with CA c
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"}
Hi,
I've written a Portfile for mozjs17@17.0.0, I've submitted it at
https://trac.macports.org/ticket/40614
It probably needs changes, and also improvements. And also I don't know if this
is the right place to ask for feedback; sorry if it isn't.
As far as I know, at least gjs depends on mozjs
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
I reply to this on my own!
On Oct 3, 2013, at 20:22 , Peter Danecek wrote:
>
> Okay, I hope that's it then with variants.
>
> I have one variant (+gsi for GSI authentication) I do not want to make
> default. However, if this is activated, I would like to an other variant to
> come with it,
Okay, I hope that's it then with variants.
I have one variant (+gsi for GSI authentication) I do not want to make default.
However, if this is activated, I would like to an other variant to come with
it, ( i.e. +ca-bundle, a bundle with CA certificates), so that the user would
get a working en
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
Well I can live with the workaround, it is not even to cumbersome. However, I
intuitively assumed it would be available, tried it and it was not. Anyway, I
think it is consistent with the logic of the system, so it would not hurt.
+1
On Oct 3, 2013, at 2:56 , Eric Gallager wrote:
> I have a
On Thu, Oct 03, 2013 at 10:35:54AM -0400, Daniel J. Luke wrote:
> the gcc manpage indicates that there's some extra magic ("Mark it as a
> system directory, so that it gets the same special treatment as is
> applied to the standard system directories.") that may or may not be
> what we want in this
On Oct 2, 2013, at 8:55 PM, Ryan Schmidt wrote:
> On Oct 2, 2013, at 19:29, Daniel J. Luke wrote:
>>> But another way to handle that issue is to replace "`-I${prefix}/include`"
>>> with "`-isystem${prefix}/include`", and several ports (like freetype,
>>> ghostscript and pianobar) do that. Which
Rainer,
Thank you for your help.
> depends_build-appendport:pkgconfig
Yes, you are right. I was not careful enough.
It seems that I don't get buildbot failure messages this time.
Takeshi
___
macports-dev mailing list
macports-dev@lists.macosforg
On 2013-10-03 08:57, Takeshi Enomoto wrote:
> BTW buildbot complains the lack of /opt/local/bin/cmake.
> Portgroup cmake is used and plplot depends on cmake so cmake should be
> installed.
> Do I have to explicitly write depends_build port:cmake?
cmake is usually already in depends_build when you
22 matches
Mail list logo
