Re: discrepancy in python policy
On Wed, Jan 31, 2007, Carlo Segre wrote: > Is the "XS-Python-Version: current" stuff replaced with something else to > flag a package that uses python-central but needs to be rebuilt for a > python transition? You wont directly find information about whether or not a package should be rebuilt in XS- fields. I think current is a fuzzy concept, and I personally prefer to express what the upstream source supports for Python versions, for example >= 2.3. In my experience, this will work as good as "current", even for packages with only private python modules and/or extensions. PS: you might want to configure a real domain in your message-ids -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: discrepancy in python policy
On Wed, 31 Jan 2007, Josselin Mouette wrote: Le mercredi 31 janvier 2007 à 14:15 -0600, Carlo Segre a écrit : I presume that this must also be changed to read that the maintainer has to install private modules explicitly. The most accurate documentation you can find (apart from specific python-support or python-central documentation) is probably the wiki, but even this one lists the "XS-Python-Version: current" insanity. Is the "XS-Python-Version: current" stuff replaced with something else to flag a package that uses python-central but needs to be rebuilt for a python transition? Carlo -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 [EMAIL PROTECTED]http://www.iit.edu/~segre[EMAIL PROTECTED]
Re: discrepancy in python policy
Le mercredi 31 janvier 2007 à 14:15 -0600, Carlo Segre a écrit : > Hello All; > > Section B.2 of the Python Policy shows a code snippet that indicates you > need to use dh_python after dh_pycentral. According to the dh_python man > page it is deprecated so this should be changed. > > In addition, just a bit further down, there is a statement that: > >"If you want python-central to handle private modules, you must pass the > list of directories containing them to dh_python (but not > dh_pycentral)." > > I presume that this must also be changed to read that the maintainer has > to install private modules explicitly. I guess the appendix could be entirely removed. The python-support part has the same mistake, plus at least two others (the useless --install-lib and the story about compiled extensions), not counting the policy itself being a bit outdated. The most accurate documentation you can find (apart from specific python-support or python-central documentation) is probably the wiki, but even this one lists the "XS-Python-Version: current" insanity. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
discrepancy in python policy
Hello All; Section B.2 of the Python Policy shows a code snippet that indicates you need to use dh_python after dh_pycentral. According to the dh_python man page it is deprecated so this should be changed. In addition, just a bit further down, there is a statement that: "If you want python-central to handle private modules, you must pass the list of directories containing them to dh_python (but not dh_pycentral)." I presume that this must also be changed to read that the maintainer has to install private modules explicitly. Cheers, Carlo -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 [EMAIL PROTECTED]http://www.iit.edu/~segre[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
