30.05.2010 21:19, Pavel Alexeev (aka Pahan-Hubbitus) пишет:
21.05.2010 20:58, Panu Matilainen пишет:Sorry for the answer to themselves.Thanks for the answers.On Fri, 21 May 2010, Kevin Kofler wrote:Pavel Alexeev (aka Pahan-Hubbitus) wrote:I think because macroses should be included before it processed as shell script. Is there some variant of %include or similar?AFAIK, no. E.g. in kde-filesystem, we end up defining things twice, once for the specfile itself and once for the .macros file: http://cvs.fedoraproject.org/viewvc/rpms/kde-filesystem/devel/kde-filesystem.spec?revision=1.49&view=markupAnd neither of you actually thought to try whether %include works? :D Hint: it does, in spec files. - Panu - Now, when bug fixed and rpm hit rawhide I can continue test it suggestion. And it does not work on strange manner - it is not produce any error, but also does nothing! So, in minimal spec file was attached in the bug I have now in %prep: %include %{SOURCE0} %{testmacros} exit 102 And at build time no TEST appeared: $ LANG=C rpmbuild -ba test.spec + umask 022 + cd /home/pasha/SOFT/rpmbuild/BUILD + LANG=C + export LANG + unset DISPLAY + exit 102 error: Bad exit status from /home/pasha/SOFT/rpmbuild/BUILD/_tmp/rpm-tmp.ECc7qg (%prep) Bad exit status from /home/pasha/SOFT/rpmbuild/BUILD/_tmp/rpm-tmp.ECc7qg (%prep) Please, can you more describe how it should work? What is prerequisites? May be link on detailed explanation? |
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel