On Jul 30, 2008, at 19:06, Ryan Schmidt wrote:
> On Jul 30, 2008, at 18:49, Rainer Müller wrote:
>
>> Ryan Schmidt wrote:
>>
>>> It's still no, but for wine and mapm3, I installed a wrapper
>>> script to set needed environment variables. Check it out. I
>>> recommend the mechanism used by mapm3;
Hello All --
I have recently written a script that parses numerous MacPorts and their
dependencies and variants information (in my collection of ports I use about
455 total). Of the total, I found one part, the libtheora port (version
1.0beta2), that produces an platform variant name of "darwin_9_
On Jul 30, 2008, at 18:49, Rainer Müller wrote:
> Ryan Schmidt wrote:
>
>> It's still no, but for wine and mapm3, I installed a wrapper
>> script to set needed environment variables. Check it out. I
>> recommend the mechanism used by mapm3; I'll change the wine
>> port's method to use ma
Ryan Schmidt wrote:
> It's still no, but for wine and mapm3, I installed a wrapper script
> to set needed environment variables. Check it out. I recommend the
> mechanism used by mapm3; I'll change the wine port's method to use
> mapm3's method soon. (Put the real binary in ${prefix}/lib/${na
On Jul 30, 2008, at 10:22, Randall Perry wrote:
I'm getting the same error trying the 5.10 install.
Can't find 'boot_File__Glob' symbol in
lib/auto/File/Glob/Glob.bundle at
lib/File/Glob.pm line 96
Verifed the file was there and the symbol was present:
[x
On Jul 30, 2008, at 06:25, Michael Thon wrote:
> The port of the ncbi_tools package would really benefit from having a
> couple of environment variables set for users at install time. When I
> took over the package I asked if there was a way for a Portfile to do
> this and the answer (at that ti
>>>
>>> I'm getting the same error trying the 5.10 install.
>>> Can't find 'boot_File__Glob' symbol in
>>> lib/auto/File/Glob/Glob.bundle at
>>> lib/File/Glob.pm line 96
>>>
>>>
>>> Verifed the file was there and the symbol was present:
>>> [xserve1:/opt/local] randy% grep boot_File__Glob
>>>
The port of the ncbi_tools package would really benefit from having a
couple of environment variables set for users at install time. When I
took over the package I asked if there was a way for a Portfile to do
this and the answer (at that time) was no. Maybe something has
changed since?