On Wed, 24 Apr 2002, Kilian Koepsell wrote: > hi, > > - about the problem of different packages depending on different versions of python: > > i think the best way would be to make different packages python2.2 and > python2.1. this is the way it is done in the debian distribution. the python > debian is just a very small package that depends on the default python version > (python2.1 in the case of debian) and that provides symbolic links to the > binaries and man pages. > > i also made the following observation: the fink .deb file contains python source >code > files (.py) as well as byte-compiled files (.pyc). the debian (linux) .deb >packages only > contain the source files and byte-compile them in the postinst script. maybe > this is the better way to handle python packages in general. >
Killian: I'd like to propose an alternative, that would make life a lot easier for me. Leave the python-2.2.1 package alone and rename the python-2.1.2 package to python21-2.1.2. The python21 package would be exactly the same as the existing python-2.1.2 package, except that the python binary would be called python21, and the package would not conflict with or replace python-2.2.1. Then, if you want to install a module (such as zope) into python21 instead of python-2.2.1, you would run "python21 setup.py" instead of "python setup.py". That way, users could have both python-2.2 and python-2.1 installed at the same time, but they would be required to explicity reference python21 to get the older python. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/CDC R/CDC1 Email : [EMAIL PROTECTED] 325 Broadway Web : www.cdc.noaa.gov/~jsw Boulder, CO, USA 80303-3328 Office : Skaggs Research Cntr 1D-124 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
