There’s two ways to change the default rpmbuild topdir: Per-User: By configuring the RPM topdir in $HOME/.rpmmacros %_topdir %{getenv:HOME}/rpmbuild Per-Project: By configuring the RPM topdir in the Makefile or on the command line rpmbuild –define ‘_topdir build’ -ba package.spec Note: in both cases, you will need to make sure your topdir directory has the appropriate … Read more
You can define rpmbuild variables with %(cmd) at the top of the spec file. Notice the command is in parenthesis, not curly brackets. An example: %define whoami %(whoami) And elsewhere in the spec file, such as a script or the build/install sections, use the variable as normal in the curly brackets like this: echo “The … Read more
From https://help.ubuntu.com/community/RPM/AlienHowto , use the alien package: Alien converts an RPM package file into a Debian package file or Alien can install an RPM file directly. This is not the recommended way to install software packages in Ubuntu. If at all possible, install packages from Ubuntu’s repositories using Add/Remove, apt-get, or the Synaptic Package Manager. … Read more
It’s not documented, but the _topdir macro determines the build area. So you can set this per-invocation with rpmbuild –define “_topdir ${PWD}/foobar” … to set the directory to whatever you want. –define is the key to setting values for any macro, not just _topdir.
$RPM_BUILD_ROOT (or the equivalent %{buildroot} SPEC file macro) always holds the directory under which RPM will look for any files to package. The RPM scripts (e.g. the script that compresses the manual pages) will also use that value to know where to look for the files that were just installed. Normally, this value will be … Read more
In fact that’s not a one but four different questions :). *) First you can quickly list a downloaded package’s dependencies/requirements by using the following commands: $ rpm -qp mypackage.rpm –provides $ rpm -qp mypackage.rpm –requires *) Second, you can use yum utility in order to satisfy these (somewhat cryptic) dependencies automatically (assuming that all … Read more
The spectool utility from the rpmdevtools package can do this. Just install rpmdevtools and point spectools at the .spec like so: spectool -g -R SPECS/nginx.spec It will download any missing sources into rpm’s %{_sourcedir} (usually SOURCES) directory.
You can install rpmbuild on MacOS using Homebrew package manager. brew install rpm This installs a bunch of packages including rpmbuild which is used to build an rpm. You can then run the following command to create an rpm rpmbuild <specfile>
Install rpmrebuild and “extract” (actually re-create) the spec file of your rpm file or your already installed package. Examples: rpmrebuild –package –notest-install -e oracle-instantclient-basic-10.2.0.4-1.x86_64.rpm rpmrebuild -s hercules.spec hercules
The –force option will reinstall already installed packages or overwrite already installed files from other packages. You don’t want this normally. If you tell rpm to install all RPMs from some directory, then it does exactly this. rpm will not ignore RPMs listed for installation. You must manually remove the unneeded RPMs from the list … Read more