On Mon, Mar 08, 2004 at 10:33:02AM -0500, 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.
Can I suggest an approach similar to jbj's mkrpm where you have a
script/makefile in the top level cvs repo which handles this. cvs.colug.net is
down atm and I don't have a local copy to hand. This is far simpler than
trying to do it via a loaded macro files.
Essentially your script/Makefile needs to just set a load of defines. Something like
rpmargs=\
--define '_ntopdir %{_topdir}' \
--define '_builddir %{_ntopdir}' \
--define '_sourcedir %{_ntopdir}' \
--define '_specdir %{_ntopdir}' \
--define '_rpmdir %{_ntopdir}' \
--define '_srcrpmdir %{_ntopdir}' \
--define '_rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm'
Then you can have targets that build setting topdir using $(pwd) or $(pwd)/%{name} or whatever
Paul
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
