Buildrequires [kitchen sink] in .spec files? (suse93& suse10)
![](https://seccdn.libravatar.org/avatar/aea1d8248292e6482742234c5cb514de.jpg?s=120&d=mm&r=g)
I've been trying to rebuild some rpms and have run into some strange build requirements. For example: to build squid, the BuildRequires statement says I need "cracklib". I can't find any requirement in squid on cracklib and indeed, squid builds find without it. So what is the purpose of "Buildrequires" statements that require packages that aren't needed to build the package? Where did these lists come from? Shouldn't the Buildrequires statements only include those packages needed by the package to build? thanks, linda
![](https://seccdn.libravatar.org/avatar/678f95ef15154106d12600b7cca9b7db.jpg?s=120&d=mm&r=g)
On 20/03/06, Linda Walsh
I've been trying to rebuild some rpms and have run into some strange build requirements.
For example: to build squid, the BuildRequires statement says I need "cracklib".
I can't find any requirement in squid on cracklib and indeed, squid builds find without it.
So what is the purpose of "Buildrequires" statements that require packages that aren't needed to build the package? Where did these lists come from?
Shouldn't the Buildrequires statements only include those packages needed by the package to build?
thanks, linda
--
Linda, I read something about this not too long ago. Sorry, I cannot remember exactly where. I think it was because some other packages that the build requires needed those specific libraries but, as you have found, it will get along nicely without them. Bit of a convoluted answer and I apologise for that. If I can find the original article I'll post it up but don't hold your breath :-) -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
![](https://seccdn.libravatar.org/avatar/5c786b1b80718534429c90c4126cd5ab.jpg?s=120&d=mm&r=g)
On Sun, 19 Mar 2006 17:05:16 -0800, Linda Walsh wrote:
Shouldn't the Buildrequires statements only include those packages needed by the package to build?
Yes it should. Until recently, SUSE used a different mechanism to specify packages needed to build a given package. These packages where listed on a line at the top of a .spec file beginning with #neededforbuild. The named packages could either be real packages or aliases for a whole bunch of packages like gnome-devel-packages pulling in everything needed to compile GNOME apps. To make the openSUSE Build Service viable, these neededforbuild where turned into BuildRequires and the list of packages trimmed down to those really needed. To err is human, so one or the other package might have been left in BuildRequires rather then be removed. If you discover something like that, please file a bug report with https://bugzilla.novell.com so that the maintainer of the package can correct it. Philipp
participants (3)
-
Kevanf1
-
Linda Walsh
-
Philipp Thomas