The filename does not affect the contents of the RPM package.
So if you set the "version" to 1, the release to "1". And then name filename:
foo-2-300.bar.rpm
RPM is going to install the package using a version of 1 and a release of 1.
On many systems, the filename is truncated to be simply "fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 20, 2008 at 5:45 PM, Nitzan Gurfinkel wrote:
> I hope I'm on the right lit and I apologize if not.
>
> During the build process the RPMs get their names through the following
> Makefile line:
>
> $(M4) -DBUILDNUMBER=$(BUILDNUMBER) -DUSER
I hope I'm on the right lit and I apologize if not.
During the build process the RPMs get their names through the following
Makefile line:
$(M4) -DBUILDNUMBER=$(BUILDNUMBER) -DUSERNAME=$(USERNAME)
-DRELEASETEXT=$(RELEASETEXT) -I$(RPM_TMPL_DIR) $(EXTRA_M4DEFINES)
$(PKGDIR)/$(RPM_TEMPLATE) > $(P
