On Monday 05 March 2007 23:26, Ian Bicking wrote: > Christoph Haas wrote: > > There is a Debian package for python-mako already. Why ship it again? > > That package shouldn't exist, it's not useful. Do you really want your > Mako just upgraded from underneath your application? Or, if you give a > firmer version requirement, do you want your application to keep anyone > else from upgrading python-mako?
Updating a package like mako silently will likely break other Debian-packaged pieces of software. Debian packages depend on each other. And on a production system it's important that software doesn't silently change. There may be API changes or new bugs. I'm running a large number of servers at work on Debian. And updating to a new stable release is always a lot of work. Imagine what has changed between Apache 1.x and 2.x. There is automatic upgrade path between these versions. The same applies to Python packages. Of course I understand that many people find easy_install a good and simple way to install Python packages. But it will destabilize an operating system that keeps track of what's installed. It may be no problem on Windows where you reinstall after a few months anyway. But my Debian system has been installed years ago and just upgraded with the time. I wouldn't want to have cruft flying around. Especially since there is no sane way to get of software I easy_install'ed. So I disagree with your opinion that Python-related software that is shipped through easy_install should blindly be used on any system. If that's what you wanted to express. Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
