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;
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 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
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?
