> > >>>gettext-devel, bison, byacc, libbzip2-devel: rpm-build >>> >>I believe no or very few packages can build without rpm-build :) >> > >Well, it's not *strictly* necessary, however the reason why I'd include >these in rpm-build is that many packages require the above packages. >And I don't think it would be right to mention all of the above in each >and every package. It's kinda like requiring gcc or glibc in every >package, no? > Why not just make a master -devel package which will requires all -devel packages, and make that a Requires in rpm-build too? Then we won't need to worry think about these things anymore.
Better yet: BuildRequires are a joke, don't you think? If you're serious about development than just install all the -devel packages! We just need to remove all BuildRequires from the packages, nobody ever uses them, and quite some (kde?) packagers are fanatical about their _wrong_ BuildRequires (see below). Better no BuildRequires than wrong BuildRequires I say. >I'd like to have a setup where I only need to specify one package and >get a whole set of needed development packages installed right away. > >Or would it be correct if I'd Require: *every* package that the new >package needs? With this I mean, that I'd require glibc, bash, >filesystem, rpm .... > Nope. Stefan PS: About the kde packages: take a look at the 7.2, 8.0, 8.1, 8.2 ifdevs in the kde packages for the BuildRequires. it's great. To bad they're just not correct: see the list of KDE packages that aren't compiling due to failed BuildRequires in http://eijk.homelinux.org/build/cooker/alpha/problem/ and http://eijk.homelinux.org/build/cooker/i586/problem/ . I've requested multiple time that this is cleaned up, but I'm ignored and my changes are reverted (of course my communication style sux, that must be it...).
