Re: how to "rembuild --rebuild" a source rpm in the current directory?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 8 Mar 2004, Robert P. J. Day wrote:

> 
> 
> On Mon, 8 Mar 2004, James Olin Oden wrote:
> 
> > On Mon, 8 Mar 2004, Robert P. J. Day wrote:
> > 
> > > 
> > >   am i close?  or am i making this far too difficult?  and what's the 
> > > format for prepending a macros file to the default list, rather than 
> > > overriding the whole list?
> > >
> > For the global stuff, have it put in /etc/rpm/macros and it will be their 
> > for your users.   For the local stuff, their ~/.rpmmacros just needs to 
> > be edited.  Whether you do this by hand, or have it automated is up to 
> > you. 
> 
> i can't do that.  the few src rpms that need to be built are part of a 
> much larger CVS checkout, and i have no control over the users or their 
> systems who check this stuff out.  in short, i can't assume that *any*
> customization has been done by these users, either personally or on their 
> systems.  for the most part, i may not even know *who* is checking this 
> stuff out, i just have to guarantee that anyone getting it can do the 
> automated build.
>
So you don't control the build systems...what a pain (-;
All is not lost, but you will have to provide a wrapper to build the rpms
if you want any sort of control of the build process.  What the wrapper
can do is:

	- generate macro files.
	- generate an rpmrc file that specifies the path to these
	  generated macro files.  You do this with the macrofiles:
	  entry wich is a colon delimited list of macros files.
	- When you run rpmbuild in the wrapper specify this generated
	  rc file (--rcfile, this too takes a colon delimited list, so 
 	  you can include the default ones after yours).

I might be missing something (if I am someone please beat me with a clue
bat), but if you want to insure that certain "macros" exist in the build 
environment, but you can't touch the build environment for the most part
I can't think of any other way to get there.  This solution does assume
you are allowed to create temporary files.

Cheers...james 


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux