On Fri, 2004-05-21 at 08:52, Panu Matilainen wrote:
> On Fri, 2004-05-21 at 08:18, Jeremy Katz wrote:
> > On Thu, 2004-05-20 at 16:19 -1000, Warren Togami wrote:
> > > The below is an example of an explicit python dependency to
> > > automatically Require a compatible version of python at build time, from
> > > fedora.us python-bsddb for FC1. Any opinions if this is a good solution
> > > in general for packages that require python?
> >
> > misa added a python-abi virtual provide that can be used instead (this
> > then also makes it so that you can have an, eg, python23 compat package
> > that would work as well). The way of querying for it is a little less
> > than ideal, though, as I'm not sure of a way other than a) hard-coding
> > or b) running rpm during the build. I guess you could do Requires:
> > python-abi = $(python -c "import sys; print sys.ver[:3]), but that seems
> > a little fragile as well.
>
> That sounds nice, too bad the provide doesn't exist in FC1 python :(
> I've been using
> Requires: %{_bindir}/python%{pyver}
> to get the major version dependency there and additional
> Requires: python >= 2.0
> ..to express "this needs at least versio foo to work" where necessary.
One more approach in the fedora.us spectemplate-python.spec: require the
site library dir and "python".
http://cvs.fedora.us/cgi-bin/cvsweb.cgi/pkg/fedora-rpmdevtools/spectemplate-python.spec?rev=.
See also https://bugzilla.redhat.com/120635
