Regarding #509697 (python 2.5 providing ctypes, and ctypes using
objdump), I don't think it's reasonable to make python2.5 depend on
binutils, just for the purpose of one of the modules in the standard
library. One option would be to add binutils to Recommends or Suggest,
but that does not ensure packages that Depend: python-ctypes will work.
Maybe "python" should stop Providing: python-ctypes, and python-ctypes
should depend on "python (>= 2.5) | python2.4" instead of just
"python2.4" (plus the recently added a dependency on binutils). This way
binutils will get pulled only when a package that depends on
python-ctypes is installed. (This does not solve, however, packages that
are being smart and are depending on "python (>= 2.5) | python-ctypes".
But maybe those packages should stop doing that.)
If this is the way to go, then for squeeze it means that, if the ctypes
source package is to disappear, it should be created as a dummy package
(from python-defaults instead?), if only to contain the binutils
depends/recommends.
Comments welcome.
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
When all is summed up, a man never speaks of himself without loss; his
accusations of himself are always believed; his praises never.
-- Michel de Montaigne
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
