On Wed, 24 Sep 2008, Joe Pruett wrote:
i finally found info on the wiki about conditionals for rpmforge
(https://rpmrepo.org/driesverachtert/DistTag). the wiki talks about dist,
but the example spec uses dtag. is dtag the right thing to use? i am
building a spec of uw-imap and want to deal
On Wed, 24 Sep 2008, Joe Pruett wrote:
is there a %error or something like that i can use for when one of the dtags
i handle isn't present?
How would you use it ?
--
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission
i think i found it. something like this:
%{?dtag:%{expand: %%define %dtag 1}}
%{?el4:%define PAMD imap.pamd}
%{?el5:%define PAMD imap.pamd.new}
%{!?PAMD:%{error:Unknown dtag = %{dtag}}}
___
suggest mailing list
suggest@lists.rpmforge.net
it looks like %{error:string} doesn't exit, just display the error. one
online doc mentions %quit, which isn't valid, but does cause the build to
stop. so now i have:
%{?dtag:%{expand: %%define %dtag 1}}
%{?el4:%define PAMD imap.pamd}
%{?el5:%define PAMD imap.pamd.new}
I guess that is possible, however it would automatically fail later if the
file %{PAMD} was not found so I don't see the point in adding checks like
this. What's more, what we usually do is make conditionals based on software
levels. So in your case it would depend on the version of pam, rather