On Mon, 21 Feb 2000, Brian J. Murrell wrote:
> from the quill of Pablo Saratxaga <[EMAIL PROTECTED]> on scroll
> <[EMAIL PROTECTED]>
> >
> > The problem is that the versions don't work with provides given by
> > Provides: line (that is they only work for package names).
>
> Hmmmm. That seems like a shortsight.
>
> > You know however the it is a correct version; so you can use --nodeps;
> > you have no choice indeed.
>
> This is ugly.
>
> > The *.spec file of kernel building is wrong; all "Provide:
> > kernel=%{version}"
> > must be changed to "Provide: kernel", no versioning can be used on
> > the Provide: line
>
> OK. Is this going to be fixed in the Mandrake kernel RPM then?
>
> > To chmou: I think the right way to handle that will be to have those
> > packages
> > just provide "kernel" (as they should) then patch rpm so for any
> > "provides"
> > it takes the version number of the package, when checking version
> > numbers.
>
> That sounds like a good idea.
>
> > Because they don't provide kernel >= 2.2.5, they provide a strange
> > thing
> > called "kernel=2.2.14"
>
> OK, I think I get this. The =, >=, etc. operators are not really
> operators on a Provides: line. They are just more characters in the
> opaque string "kernel=2.2.14" feature that the package provides. That
> sucks. :-)
>
> > As you have no package that provides "kernel" then any package
> > requiring
> > it will fail.
>
> Even worse, I have no package that provides the opaque feature "kernel
> >= 2.2.5" so packages that are written to Require: kernel >= 2.2.5 will
> not work. This seems very unworkable. I don't think we should be
> putting single version specific strings like ">= 2.2.5" in Requires:
> attributes.
>
> Comments?
>
> b.
it's a spec bug, it reads
Provides: kernel=%{version} module-info kernel-fb
it should read.
Provides: kernel = %{version} , module-info, kernel-fb
Shouldn't it?
--
MandrakeSoft http://www.mandrakesoft.com/
--Axalon
