Re: Forcing a script to bomb, etc.
Michael Jennings <[email protected]>
| Newsgroups | gmane.linux.redhat.rpm.general |
|---|---|
| Message-ID | <[email protected]> |
On Friday, 12 October 2007, at 10:10:13 (-0700),
Philip Prindeville wrote:
> So... a few miscellaneous questions.
>
> First, where is the current authoritative documentation? I've not found
> %{!? documented anywhere.
/usr/share/doc/rpm-*/conditionalbuilds
> Second, is there a guide to what macros are common on all platforms, like
> %{with and %{without?
Not really, but the stuff in /usr/share/doc is a good start.
> Third, can I force an RPM to error with a message is a standard
> fashion, if it finds (for instance) that it's being built with a
> combination of incompatible --with options?
It's a shell script. Do whatever you like.
> Fourth, is it philosophically preferable to have a package build by
> default with everything, but have the package turn stuff off with
> --without xxx, or build the smallest supportable package, but turn
> things on via rpmbuild --with arguments?
It's your package; do it however you want. I prefer to default to
building everything and require manual intervention to turn things
off. Makes things more autobuilder-friendly.
> Lastly, where's the documentation on writing and using macros that take
> arguments?
See above.
Michael
--
Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[email protected]>
Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org)
-----------------------------------------------------------------------
"Give a man a fish, you feed him for a day. Teach a man to fish, he
spends all his time in the basement tying flies and neglecting his
personal hygiene." -- NewsRadio