John Goerzen <jgoerzen@complete.org> wrote:
> There are a lot of unnecessary dependencies on specific Python
> versions out there.
Wouldn't the use of virtual packages could help this out. Let's say you
have a python application and module library foo. The source package is
called "foo". Multiple binary packages are created for foo as
pythonX.Y-foo, each with a Provides: "foo". Package bar depends upon
"foo", but doesn't care which is used. python2.1-foo, python2.2-foo,
and python2.3-foo all satisfy the dependency.
Some people provide a dummy python-foo package to track the default
python installation. Should the default python installation change, it
wouldn't matter a whole lot, only the dummy package needs to be removed
for the upgrade. Still, I'm not convinced the dummy package is all that
necessary.
On Mon, Jan 05, 2004 at 08:04:44PM +0100, Marc Haber wrote:
> Which is a big part of the python problems that Debian has at the
> moment.
These issues are being discussed on debian-python for those that want
the up-to-date status of Python on Debian.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
Attachment:
signature.asc
Description: Digital signature