Matt Pounsett wrote: ...
Now, I realize that the easy and obvious way to manage this is to have one spec file each for Bar and Baz, which each have two %package sections for the -client and -server halves, and appropriately set co-requisites -- four RPMs in total. However, I'd like to have a single spec file, which takes the Bar-1.3.tar.gz and Baz-1.0.tar.gz source files, does the configure and build for both, and creates only two RPMs -- Foo-plugins-client and Foo-plugins-server. This gives me fewer spec files to maintain, and fewer RPMs to move around when setting up new machines.
Is this at all possible? If so, can anyone point me to some docs that explain how to build the spec file appropriately, or even just an example SRPM I can look at to see how this functions?
Thanks muchly..
Hints:
Source0: Bar-1.3.tar.gz Source1: Baz-1.0.tar.gz ... %setup -a 1
I think '-a' is what you are looking for here... I haven't really used it much, so you'll have to do some leg work before the above hint is really useful.
HTH,
Eli --------------------. "If it ain't broke now, Eli Carter \ it will be soon." -- crypto-gram eli.carter(a)inet.com `-------------------------------------------------
------------------------------------------------------------------------ Confidentiality Notice: This e-mail transmission may contain confidential and/or privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or reliance upon the contents of this e-mail message is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that proper delivery can be arranged, and please delete the message from your computer. Thank you. Inet Technologies, Inc. ------------------------------------------------------------------------
