From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Description of problem: Hi All, I am using White Box Enterprise Linux 4 (WBEL 4). To recompile a scr RPM, I am now required to run a program called "rpmbuild." Problem: the "rpm" for it, which resides on disk 3, has a different name: rpm-build (the difference being the dash). For those unaware of the fact, having a different names makes it very hard to find. Please use the same name on the rpm as the program uses. find /cd -iname \*rpmbuild\* -print Many thanks, --Tony Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. please see discription 2. 3. Additional info:
Many packages have binaries with differing name to package name. 1) install selecting the Development group gets you rpmbuild 2) use a depsolver to find/install the package - eg yum provides /usr/bin/rpmbuild 3) White Box bugs should go against their distribution not here.
1) install selecting the Development group gets you rpmbuild The installer, "upgrade option," has no "install additional packages" option. You have to risk trashing your installation by using the "install option." See bug 159611 2) use a depsolver to find/install the package - eg yum provides /usr/bin/rpmbuild Oh, I really, really want to do this over a dial up modem! It is much better to have the rpm's named after the actualy packages they install and look for them on your install disks. 3) White Box bugs should go against their distribution not here. The maintainer of WBEL sends you here. This is the proper place. Why in the world would you want to be cut off from such a valuable source of feedback? Please reopen this bug. Many thanks, --Tony
If you didn't install development tools in the first place you aren't going to have much joy with just rpm-build, you'll need m4, make, autotools, loads of libraries too. This is possible to do by hand chasing deps, but using a depsolver is really the supported method here. I understand b/w being an issue but you can create a local repository from your install media and use a file:// url in your yum repo conf file. man createrepo man yum.conf Many rpms provide more than one binary - should we call each rpm the concatenation of all the files in it? The information is in the rpm header header and repodata which is queryable by tools such as repoquery, yum, etc.