2008/1/10, Josselin Mouette <[EMAIL PROTECTED]>: > * The python module is built in /usr/lib instead > of /usr/lib/python2.X/site-packages; this is probably an > upstream issue but you can work around it without patching.
I guess I can simply move the module to the appropriate directory. > * The Debian build process only builds the package for one python > version; this way the module built for python2.4 will not work > with python2.5. You must loop over the supported python versions > to build the module for each of them, and install it in each of > the corresponding /usr/lib/python2.X/site-packages directories. > This means I will need to build all of the hamlib related packages for the different python versions in Debian (I need to start the build process all over again for every python version). There is no way in the hamlib source to only build the python module. This isn't very elegant. > There are examples of how to do that in the python-support documentation > and on the wiki. If you need help, please don't hesitate to ask for a > patch. > I have looked over the docs and wiki a couple of times. It is hard to understand for a python outsider. There are so many issues, it's all very confusing. So, yes a patch would be very much appreciated to have this resolved! > > Cheers, > -- Thanks, Joop pa3aba at debian dot org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
