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
rpmbuild -bb –define ‘_foobar Foo’ somespecfile.spec and refer it within the spec as %{_foobar} (the _ is a convention, not a must)
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.
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.
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
You can use the yum-builddep command from the yum-utils package to install all the build dependencies for a package. The arguments can either be paths to spec files, paths to source RPMs or the names of packages which exist as source RPMs in a configured repository, for example: yum-builddep my-package.spec or yum-builddep my-package.src.rpm The same … Read more
I often do binary rpm per packaging proprietary apps – also moster as websphere – on linux. So my experience could be useful also a you, besides that it would better to do a TRUE RPM if you can. But i digress. So the a basic step for packaging your (binary) program is as follow … Read more