On Thu, 18 Feb 2010 22:26:12 +0200 (EET)
Panu Matilainen <pmatilai(a)laiskiainen.org> wrote:
On Wed, 17 Feb 2010, Till Maas wrote:
> On Mon, Feb 15, 2010 at 06:58:42PM -0600, Garrett Holmstrom wrote:
>> 2010/2/14 Till Maas <opensource(a)till.name> wrote:
>>> %{buildroot} probably fits best in the "Other macros" section,
>>> because it is a macro to be used inside the spec. Bug the
>>> %{_buildrootdir} macros like the other RPM directory macros is
>>> afaik supposed to be used only with rpmbuild --define to change
>>> the behaviour of rpmbuild.
>>
>> Was typing the nonexistent %{_buildroot} instead of %{buildroot} a
>> typo?
>
> Yes, I just fixed this.
>
>> On a somewhat related note, some directory macros (e.g.,
>> %_keyringpath) contain trailing slashes, while others don't. Does
>> this matter enough to be worth addressing?
>
> %_keyringpath is not mentioned at all and according to 'rpm
> --showrc | %grep "/$"' it is the only macro with a trailing slash.
> So maybe this can just be changed. But it also does not hurt that
> much, because afaik a double slash in a path will be handled like a
> single slash.
%_keyringpath is nothing packagers should be concerned with. Neither
is %_buildrootdir. These are rpm internals, unfortunately the macro
namespace is well and thoroughly mixed up wrt what "internal" and
whats not.
Another couple of macros that are occasionally useful in specs are
%{_builddir} and %{buildsubdir} - could they be added too?
Paul.