#1045 WIP: Add discussion of macro names beginning with underscores.
Closed by james. Opened by tibbs.
tibbs/packaging-committee underscores  into  master

Download 1045.patch

This extends the existing mention of macro forms of system executables.

I wanted to capture the rule that you shouldn't be using underscored macro names unless it is to set them to influence RPM behavior, so I tried to extend the existing rule about not using things like %__rm. I'm having trouble with the phrasing so any suggestions are appreciated.

Metadata Update from @tibbs:
- Pull-request tagged with: meeting

:thumbsup:

What about

However, in some cases it might not be possible to avoid using a macro prefixed with underscores.
If that is the case, the macro named with leading underscores MAY be used.

Or even:

The packaging committee would like to be notified of such cases.

This imples two or more underscores, right?
Maybe "2+" should be explicit. One underscore is fine (c.f. _bindir, _libdir, etc.), right?

Yes, that was one of the questions I needed to ask in the meeting. The consensus was to limit to 2+ underscores but I have not yet reworked the PR.

Metadata Update from @james:
- Request assigned

Ported and merged the initial commit via.

https://pagure.io/packaging-committee/pull-request/1221

...going to close this PR, but everyone feel free to open new PRs for any changes/updates you want.

Pull-Request has been closed by james

Metadata