Re: Dependency on rpmlib

["Andrea Sciaba'" <Andrea Sciaba cern ch>]

Jeff Johnson wrote:
> On Thu, May 02, 2002 at 03:26:20PM +0200, Andrea Sciaba' wrote:
>
> > Hello,
> > I am building some rpms using version 3.0.5, and I have found out that 
> > if I specify explicitly a particular version of a required package in 
> > the Prereq: tag, like for example:
> >
> > Prereq: anaphe-cms = 3.6.6
> >
> > the rpm is built with this dependency:
> >
> > rpmlib(VersionedDependencies) <= 3.0.3-1
> >
> > while if I use
> >
> > Prereq: anaphe-cms
> >
> > that dependency is not there.
> >
> > Can anybody explain it?
>
> Sure. Before rpm-3.0.2, rpm did not support versioned PreReq:'s.
>
> When a possibly incompatible feature is used when building a
> package, then rpm adds a tracking dependency in order to associate
> the new-fangled feature with a version of rpm that can handle the feature.

I do not follow the logic. If versioned dependencies did not exist 
before 3.0.2, why rpmlib <= 3.0.3-1? I would rather expect something 
like rpmlib >= 3.0.2-1...

Cheers,
Andrea Sciaba'