Heya,
currently, I'm facing a strange situation: In one of my packages[1], I
have a moderate number of patches
Patch0001: 0001-Don-t-access-the-net-while-building-docs.patch
Patch0002: 0002-disable-debug-move-web-root.patch
Patch0003: 0003-change-lockfile-location-to-tmp-and-also-add-localho.patch
....
Instead of using
%patch0001
%patch0002
etc.
I wanted to give a shot to a somewhat different approach: using the
%{patches} macro. Sadly, that macro is empty. I could verify, e.g by
cloning the f20 branch of libguestfs, the macro and the cool approach
there really works:
%prep
%setup -q
# Use git to manage patches.
# http://rwmj.wordpress.com/2011/08/09/nice-rpm-git-patch-management-trick/
git init
git config user.email "libguestfs@xxxxxxxxxx"
git config user.name "libguestfs"
git add .
git commit -a -q -m "%{version} baseline"
git am %{patches}
So: the question is: how to debug the macro expansion? invocation is the
same, for libguestfs (where it works) and for python-django-horizon,
where it doesn't.
Any hints or pointers are welcome!
Thanks,
Matthias
[1]
http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/tree/python-django-horizon.spec#n25
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging
