Re: Debhelper support should be ready tomorrow
On Mon, Jun 12, 2006 at 09:06:43PM +0200, Raphael Hertzog wrote: On Mon, 12 Jun 2006, Raphael Hertzog wrote: On Mon, 12 Jun 2006, Raphael Hertzog wrote: I would love to have this fixed by today's dinstall. That's why I prepared the attached NMU, please just send an OK and I'll upload it (of course, feel free to do it yourself in a maintainer upload). Without any answer from you, I might upload it right before dinstall (depending on the opinion of other involved people). Just to avoid confusion, this would mean uploading between 18:00 and 19:00 UTC today (in about 9.5 hours). Debhelper uploaded. We also had a python-central upload (fixing dh_pycentral) and a python-support (adding dh_pysupport). So hopefully we should be able to really start updating modules to the new policy tomorrow. Build-Depends will have to require: - python (= 2.3.5-7) (for pyversions script) Are packages expected to call pyversions directly, or is this something that should be a versioned dep from one of the other build-dependencies? Hmm, I guess it's called by dh_python, and debhelper doesn't depend on python at all. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debhelper support should be ready tomorrow
On Mon, 12 Jun 2006, Joe Wreschnig wrote: - python (= 2.3.5-7) (for pyversions script) Okay, I've updated the policy document to use that version in the Build Dependencies section. Which is only really needed for extensions. Modules don't need more than an unversioned dependency on python / python-dev. Extensions will also need a build-dep on python-all-dev. Are packages expected to call pyversions directly, or is this something that should be a versioned dep from one of the other build-dependencies? Some packages will call pyversions themselves to get the available list of Python versions, and run each one on setup.py (see [EMAIL PROTECTED] for an example). Pure Python modules using python-support won't need to. ... using python-support or python-central BTW. Hmm, I guess it's called by dh_python, and debhelper doesn't depend on python at all. No, pyversions is not (yet) used by dh_python. I don't need to know which versions I'm building but which version I have built... If we want dh_python to fail when the versions built do not match what has been announced in XS-Python-Version, then I might start using it (but I have perl code to do the same since it was in my first dh_python). -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debhelper support should be ready tomorrow
Raphael Hertzog writes: On Mon, 12 Jun 2006, Joe Wreschnig wrote: - python (= 2.3.5-7) (for pyversions script) Okay, I've updated the policy document to use that version in the Build Dependencies section. Which is only really needed for extensions. Modules don't need more than an unversioned dependency on python / python-dev. Extensions will also need a build-dep on python-all-dev. except if you build an extension for just the default version. Hmm, I guess it's called by dh_python, and debhelper doesn't depend on python at all. No, pyversions is not (yet) used by dh_python. I don't need to know which versions I'm building but which version I have built... If we want dh_python to fail when the versions built do not match what has been announced in XS-Python-Version, then I might start using it (but I have perl code to do the same since it was in my first dh_python). we should detect that. the resulting package will not be usable? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
