[Distutils] Re: CPAN functionality for python
bsass at freenet.edmonton.ab.ca
Tue Feb 27 04:54:29 EST 2001
This confirms what I got out of another list member in p-email...
all the problems surrounding RPMs I hear about are most likely the
result of inexperienced packagers.
Debian can have the same problems, but the packaging tools are
thorough enough that things usually work, even if the result is really
ugly (e.g., the Active State py-2.0 .debs <shudder>).
On Mon, 26 Feb 2001, Sean Reifschneider wrote:
> On Mon, Feb 26, 2001 at 12:22:47PM -0700, Bruce Sass wrote:
> >I think the problem with RPMs is that they depend on a specific
> >package, instead of depending on the contents of a package.
> In RPM, you can let the packaging system decide what revisions of
> various packages are needed (by looking at the results, it will
> find out what libraries it links against, what's in the she-bang
> (#!) lines, etc). That mechanism is usually the most paranoid
> about versions (if we linked against glibc 220.127.116.11.pi, then that's
> exactly what we expect).
> On the other hand, if you know better, as an application developer,
> you can include something like:
> Requires: python >= 1.5.2
> in the .spec file which says "I know that 1.5.1 won't work, but I hope
> that 1.6 won't break this package".
More information about the Python-list