hello,
in my private code stash I now have the following RPM macro:
# (d)rop shebang (interpreter) line:
%update_shebang -d
# (s)et shebang (interpreter) line to /usr/bin/foo:
%update_shebang -s /usr/bin/foo
This is useful for python, but i don't want to put this in python-rpm-macros because it is going to
be useful for other packages and languages as well.
Instead I'd prefer to put this into /etc/rpm/macros.shebang, or /usr/lib/rpm/macros.d/macros.shebang
(which of the two is preferred these days btw?)
But I'm faced with the question of how to package it. ISTM this should be part of the default build
environment. If we need a BuildRequires: shebang-macros, we can as well stick with adhoc "sed"
invocations in every package.
So i'd create the shebang-macros package and add it as Requires for ... what? rpm-build? rpm itself?
Maybe instead add the macro to rpm and push upstream?
This fully implicit installation won't be portable to other distros though. What then, invoke the
macros always as %{?update_shebang:%update_shebang -d} ? That seems stupid.
Maybe I'd keep it as a requirement to python-rpm-macros, and other potential users (perl, ruby) can
add it as a requirement to their respective macro sets too?
what do you folks think?
m.
