On Sat, Mar 31, 2001 at 01:06:48AM +0200, M.-A. Lemburg wrote:
The reason is simple: the Python API has changed between versions and also the path used by the files inside the packages use the major.minor version number.
The same problem most probably also occurrs for bdist_dumb archives and most other binary distribution formats.
With rpm and probably other package formats like deb, you can have a requires that indicates the version of python needed for installation. E.g. if you place Requires: BeOpen-Python = 2.0 in the spec file, the resulting rpm won't install on systems without python 2.0 user intervention. Similarly a BuildRequires tag allows for specifying dependencies in the build process although I don't think it is very applicable to bdist.
--
Suchandra S. Thapa s-thapa-11@alumni.uchicago.edu
In article 20010331002410.B815@hepcat.telocity.com, s-thapa- 11@alumni.uchicago.edu writes ...
With rpm and probably other package formats like deb, you can have a requires that indicates the version of python needed for installation. E.g. if you place Requires: BeOpen-Python = 2.0 in the spec file, the resulting rpm won't install on systems without python 2.0 user intervention. Similarly a BuildRequires tag allows for specifying dependencies in the build process although I don't think it is very applicable to bdist.
I thought a desirable feature of distutils was to break away from the specialised distributions and create an automatic build system. Why do I need an rpm if I can down load and build from source? Is it the manager
people who need these labelled lumps?
Robin Becker
Robin Becker wrote:
In article 20010331002410.B815@hepcat.telocity.com, s-thapa- 11@alumni.uchicago.edu writes ...
With rpm and probably other package formats like deb, you can have a requires that indicates the version of python needed for installation. E.g. if you place Requires: BeOpen-Python = 2.0 in the spec file, the resulting rpm won't install on systems without python 2.0 user intervention. Similarly a BuildRequires tag allows for specifying dependencies in the build process although I don't think it is very applicable to bdist.
I thought a desirable feature of distutils was to break away from the specialised distributions and create an automatic build system. Why do I need an rpm if I can down load and build from source? Is it the manager people who need these labelled lumps?
Today, there are probably more Linux users out there who cannot compile their own code, than ones which do know how this works, either way, we'll have to make binaries available for the sake of customer support.
BTW, most downloads go for the binary versions, either the Windows installers or the Linux RPMs.
-- Marc-Andre Lemburg
Company & Consulting: http://www.egenix.com/ Python Pages: http://www.lemburg.com/python/
On Sat, Mar 31, 2001 at 07:28:35AM +0100, Robin Becker wrote:
I thought a desirable feature of distutils was to break away from the specialised distributions and create an automatic build system. Why do I need an rpm if I can down load and build from source? Is it the manager people who need these labelled lumps?
Even ignoring those people who don't want to install gcc and development tools, some modules may need new software to be built. For example, I believe PyQT needs SIP. If you already have SWIG installed, I'm not sure whether you want to download and install SIP just to compile PyQT. Similarly, people may not want to install bison, yacc, assorted development packages, etc. just to compile a module especially if they won't use them again.
--
Suchandra S. Thapa s-thapa-11@alumni.uchicago.edu
-
M.-A. Lemburg -
Robin Becker -
s-thapa-11＠alumni.uchicago.edu