Re: How are OpenPegasus "rpm's" constructed after you have executed "make build" ?

Roger,

Thanks for pointing out the RPMMakefile. So many files, so little time.


On Wed, Feb 24, 2010 at 4:38 PM, Kumpf, Roger <[email protected]> wrote:

>  John,
>
>
>
> Check out pegasus/Makefile.Release and pegasus/rpm/RPMMakefile.  Also of
> interest:  pegasus/doc/BuildAndReleaseOptions.html.
>
>
>
> -Roger
>
>
>
> *From:* John Robinson [mailto:[email protected]]
> *Sent:* Wednesday, February 24, 2010 1:16 PM
> *To:* Steve Peters
> *Cc:* [email protected]
> *Subject:* Re: How are OpenPegasus "rpm's" constructed after you have
> executed "make build" ?
>
>
>
> If that is the case, then why are there so many variables that are
> specified in the Linux version of the "env_var_Linux.status" file used for
> Linux builds that appear to be only used for "RPM" builds?
>
>
>
>
>
>
>
>
>
>
> On Wed, Feb 24, 2010 at 4:10 PM, Steve Peters <[email protected]>
> wrote:
>
>
>
>
>
>  I think you are looking for something that isn’t there. We had to create
> our own installation ( rpm, installshield, … ) for the OSes
>
> we support.
>
>
>
>                         Steve Peters
>
>
>  ------------------------------
>
> *From:* John Robinson [mailto:[email protected]]
> *Sent:* Wednesday, February 24, 2010 12:56 PM
> *To:* [email protected]
> *Subject:* How are OpenPegasus "rpm's" constructed after you have executed
> "make build" ?
>
>
>
> Where is the process for constructing and tailoring OpenPegasus rpm's for
> linux documented. If it is not documented, then, how is it done.
>
>
>
> I finally figured out that there is apparently no "install" command in the
> Makefile. I presume this is because installation is done by constructing a
> rpm based on the "rpm" directory and then installing the rpm.
>
>
>
> Note. I have never constructed a rpm (except from a "srpm").
>
>
>
> Any help be appreciated.
>
>
>