Re: Re: Re: [crossfire] Is the deposit bu g on the bank PYò0script ever going to get fixed?
Todd Mitchell
temitchell at sympatico.ca
Wed Feb 23 20:15:49 CST 2005
I really think the best way to do this is to keep the check we have now but let intelligent agents (like us peepuls) provide a path to python when calling the configure script which will override it. If you wish you should be able to say:
./configure --have-python=/usr/local/include/python307.1
The responsibility should fall on the agent to ensure if this is used it is used properly - who can deny a cf admin a specially blessed python 1.5, which they may want for religious reasons - with full knowledge that it will preclude the use of many existing scripts and functions. Any additional checking, automation or packaging seems to me to be a bit overkill.
>
> So if you compile against say python 2.1 library, dynamic linking with the
>
> 2.4 library may not work (or could certainly get the case of not picking up
>
> the new feature or something).
>
>
Oh for sure. This is exactly when the runtime checking would come in
>
handy - as long as the developers were sure they knew how different
>
versions would react. In this case it would make sense to only link
>
against system libs (rather than the ones you brought with you) if you
>
were absolutely sure all would be well.
>
>
Rob
>
>
--
>
Robert Brockway B.Sc.
>
Senior Technical Consultant, OpenTrend Solutions Ltd.
>
Phone: 416-669-3073 Email:
rbrockway at opentrend.net
http://www.opentrend.net
>
OpenTrend Solutions: Reliable, secure solutions to real world problems.
>
Contributing Member of Software in the Public Interest (
http://www.spi-inc.org
)
>
>
_______________________________________________
>
crossfire mailing list
>
crossfire at metalforge.org
>
http://mailman.metalforge.org/mailman/listinfo/crossfire
More information about the crossfire
mailing list