On 2016-6-1 03:34 , Mojca Miklavec wrote:
On 27 March 2016 at 17:33, Rainer Müller wrote:
On 2016-03-27 16:57, René J.V. Bertin wrote:
Can someone please summarise the exact priority rules used in
resolving the file to be included when using a PortGroup statement in
a port?
1. _resources/port
On 27 March 2016 at 17:33, Rainer Müller wrote:
> On 2016-03-27 16:57, René J.V. Bertin wrote:
>> Can someone please summarise the exact priority rules used in
>> resolving the file to be included when using a PortGroup statement in
>> a port?
>
> 1. _resources/port1.0/group/*.tcl in ports tree of
I've sent in a Portfile for apache-geode, Milestone 2. Since I don't
see it in the list of available ports, I'm guessing it's not yet been
looked at.
Hopefully, in a few weeks I'll be updating it with Milestone 3.
___
macports-dev mailing list
macports-
On Tuesday May 31 2016 09:31:02 Brandon Allbery wrote:
> On Tue, May 31, 2016 at 4:24 AM, René J.V. wrote:
> Is there some reason you can't invert the logic?
I don't see how, not if you have things to be done on one platform and other
things to be done on another. That's why I used if/else cons
On Tue, May 31, 2016 at 9:24 AM, Marcus Calhoun-Lopez wrote:
> /usr/bin/defaults exists and is working.
> The foreach loop seems to be looping over the correct values.
> For some reason, however, /usr/bin/defaults seems to be either
> (1) failing to create Info.plist (but doing so without gen
On Tue, May 31, 2016 at 4:24 AM, René J.V. wrote:
> That's a pity. I had quite a few if {${os.platform} eq "darwin"} {} else
> {} statements in certain of my ports, which I most all replaced with
> platform statements at the suggestion to do so.
Is there some reason you can't invert the logic?
In the octave port, I have the following code:
set appName Octave.app
...
foreach {key value} ${values} {
system "/usr/bin/defaults write ${worksrcpath}/${appName}/Contents/Info
${key} ${value}”
}
where values is a list.
/usr/bin/defaults exists and is working.
The foreach loop seems to be
On 2016-05-31 10:24, René J.V. Bertin wrote:
> Would it be hard (and potentially acceptable) to extend the syntax to
>
> platform ... {
> } else {
> }
>
> of something of the sort? That seems like it might require patching the Tcl
> source code.
The definition of the platform proc is here:
htt
On Sunday May 29 2016 10:14:53 Ryan Schmidt wrote:
>Correct, you can't use a platform statement to do that, so use an if
>statement.
That's a pity. I had quite a few if {${os.platform} eq "darwin"} {} else {}
statements in certain of my ports, which I most all replaced with platform
statement
On May 27, 2016, at 4:31 PM, Sean wrote:
> Looking to create a portfile for a package that only distributes pre-compiled
> binaries.
>
> In this case, package.tbz expands to:
>
> package
> └─ bin/
> └─ share/
> └─ lib/
>
> Is the most idiomatic way to eliminate the config, build, and test ph
On May 30, 2016, at 6:33 AM, Mojca Miklavec wrote:
> On 29 May 2016 at 20:19, Chris Gorman wrote:
>> Hello,
>>
>> I was wondering how to inspect variables in a port file. Specifically, I
>> want to apply a patch conditionally if perl is version 5.10.0.
>>
>> I'm trying something like
>>
>> i
11 matches
Mail list logo
