On Thu, 2002-04-25 at 12:37, Fran�ois Pons wrote: > Brad Felmey <[EMAIL PROTECTED]> writes: > > > On Thu, 2002-04-25 at 07:44, Fran�ois Pons wrote: > > > Andrei Ivanov <[EMAIL PROTECTED]> writes: > > > > > > > I tried with curl-7.9.6-1mdk.src.rpm from cooker but the same thing > > > > happens. What can I do ? Is this the right way to update a package ? > > > > > > macros have changed, please upgrade all rpm stuff for that, or change to > > > %configure instead, it could be enough (some other macros may fails ?). > > > > If it requires a certain level of rpm to compile, should not then that > > level of rpm be listed in buildrequires? I ask this because I guess I'm > > having trouble understanding this process. I've seen rpms that need a > > certain something that's not in the spec, and the answer was "use > > cooker". Okay, but if a package requires certain things, then those > > certain things should be listed in the requires regardless, should they > > not? I thought that was the whole purpose of having requires in the > > first place. > > Macros are changing from rpm between various distribution, this was especially > the case between a 7.0 to 8.0, between 8.1 and 8.2, there should be not too many > changes so you can try without upgrading rpm (but with modifying the spec file). > > If we have to add such level, this will be done automatically problably and you > have to get rpm of distribution requested all the time. This information is not > maintained by maintainers most of the time currently but we can add it.
Okay, I can see where it would be difficult to put requires for everything under the sun, but how about as a general rule adding them as they become known? For instance, in this case we now know that curl requires rpm 4, and so we will have rpm >=4.x entered into the requires. Yes, no, or did I completely misunderstand what you wrote? -- Brad Felmey
