Re: RPMMakefile

My troubles with building RPMs on CENTOS and RHEL 5.4 seem to be now
resolved.

The core issue for the simplest of RPM builds is to not define either
PEGASUS_ROOT nor PEGASUS_HOME in either the unix environment nor the
"env_var_Linux.status" file.

If the PEGASUS_RPM_DIRECTORY variable is defined, one may even do builds as
other than root.

I found  it necessary to comment out the following two variables:
PEGAUS_OVERRIDE_PRODUCT_ID and PEGASUS_OVERRIDE_DEFAULT_RELEASE_DIRS

It was necessary to make minor modifications to the RPMMakefile to support
RHEL version 5.4 and the CENTOS clone distribution of RHEL.




On Wed, Mar 10, 2010 at 1:18 PM, John Robinson <[email protected]> wrote:

> If a developer is trying to build rpms and srpms without being root, it is
> natural to define PEGASUS_RPM_DIRECTORY.
> It appears that if one does that, then the source tar is renamed to
> tog-pegasus in the $PEGASUS_RPM_DIRECTORY/SOURCES directory.
>
> Is there any reason for this behavior.  I am seeking to build the RPMS on a
> CentOS 5.4 system. It appears that RPMMakefile is targeted for just REDHAT
> and SUSE without
> a generic fallback based on the defaults of the RPM installation.
>
>