Re: help with writing a PEP to ease software distribution
On Wed, Oct 01, 2008 at 11:33:03AM +1000, Ben Finney wrote: Huge thanks to Josselin Mouette +10 -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with writing a PEP to ease software distribution
Nicolas Chauvat [EMAIL PROTECTED] writes: Could some people from the Debian-Python team help out with this? […] Would you mind joining the discussion on distutils-sig at http://www.python.org/community/sigs/current/distutils-sig/list/ ? Huge thanks to Josselin Mouette and all others for ongoing effort in the above discussion, presenting clear, positive explanations about exactly what will improve operating system package maintainers's lives when dealing with Python “distributions”. It's a great step forward from hearing only “distutils sucks, and setuptools is worse” to the current ongoing discussion with the Python distutils people on specifically how to improve the situation. Keep it up, folks! -- \ “If I haven't seen as far as others, it is because giants were | `\ standing on my shoulders.” —Hal Abelson | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
help with writing a PEP to ease software distribution
Hi List, I started with a troll on the pycon-uk list. The discussion landed on distutils-sig. It looks like it may end up with something good. Here are the public threads: http://mail.python.org/pipermail/distutils-sig/2008-September/010007.html http://mail.python.org/pipermail/distutils-sig/2008-September/010010.html Here is where we stand today: http://mail.python.org/pipermail/distutils-sig/2008-September/010126.html Could some people from the Debian-Python team help out with this? At Logilab, we have been making Python packages for years, but we are not the authors of python-support nor python-central nor the Debian Python Policy and what would be really nice were that these people contribute to the PEP for they have even more experience than we do. Making a consistent and spell-checked document and advocating it I can do. Doing the necessary reading, testing and writing it alone I do not have time. Would you mind joining the discussion on distutils-sig at http://www.python.org/community/sigs/current/distutils-sig/list/ ? -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help with writing a PEP to ease software distribution
Le lundi 29 septembre 2008 à 15:12 +0200, Nicolas Chauvat a écrit : Here is where we stand today: http://mail.python.org/pipermail/distutils-sig/2008-September/010126.html This looks like a step in the right direction if we want to generate inter-module dependencies. Most things defined in the PEP will not be useful for packaging, except for making something like a dh_make_python almost trivial to write. The one thing that we’d almost certainly use is the Requires and Provides fields. However you should be careful with the notion of version. It is nice to have a lot of flexibility in specifying versioned dependencies, but the more stuff the norm allows, the more complicated it will be to translate this into inter-package dependencies. For example, if you require a minimal version of 1.4, you can translate this to a package version of 1.4; it is a bit hackish but will work if you handle epochs correctly. But if the package you depend on has a Provides: blah (1.4), you have no way to map that to a dependency, because you can’t know what other versions of the package will provide. In all cases, it will be necessary to manually add shlibs-like information to the packages; they could be partly autogenerated like symbol files, but you need a mapping between provided modules and the first version of the package that provides it. Cheers, -- .''`. : :' : 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
