M.-A. Lemburg wrote:
Finally, I think it's important to note that what Debian should or should
not use isn't really relevant to Debian's users, who will quite simply need
eggs for many packages. If Debian doesn't provide them, the users will be
forced to obtain them elsewhere. Over time, the number of packages that
users need in egg form will continue to increase, and there will be an
increasing number of users wanting to know why Debian can't provide
them. It's perfectly reasonable not to redo existing Debian packages to
use eggs, but for some packages, *not* using eggs is simply not an option.
Why should "eggs" be the only way to install a package ?
Doesn't the standard "python setup.py install" work with
eggified packages anymore (meaning that the package is
installed as normal site-packages package) ?
Eggs give room for package metadata that doesn't exist otherwise.
Putting dependencies aside, this is functionality that simply doesn't
exist with the standard distutils installation. In the case of
FormEncode, it doesn't make use of any egg features (except that other
packages may want to depend on it using setuptools). In the case of
other frameworks -- including TurboGears (which I think is the ultimate
packaging goal here) -- the Egg metadata really is important, it's not
just used for dependencies.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
