in a version independent world if a package did not work then the bug ciould be filed to the source developer (and maybe to the package maintainer because they may be able to patch to make it work if they are knowledgable enough)
]]>whether or not some sort of collating of python libs is possible would be something to bring up to the devs ... ultimately it saves them time if more order can be introduced.
]]>if you do have to manually set that placement of files then yes i believe that you are correct with your comments. generally python dependent packages would have to be rebuilt upon release of a new version. thankfully the list is much smaller than perl dependent packages.
]]>The default for python is /usr/lib/python2.3/site-packages/, correct?
Well, when python 2.4 comes out, all these PKGBUILDs need updating...
The python installation scripts (packages that come with build.py) can install to a version independent location (defaults to /usr/lib/[LibraryName]/)... should this be done with all python packages? If so, then /etc/profile.d/ needs updating so python can search for libraries in that location...
Any ideas/comments?
]]>