#1206 %pyproject_buildrequires: Don't confuse packagers with implied -r
Merged 2 years ago by churchyard. Opened 2 years ago by churchyard.
churchyard/packaging-committee pyproject_buildrequires_no_r  into  master

@@ -1445,13 +1445,16 @@ 

  The macro has these options:

  +

  ** `+-R+`: Don't include run-time requirements (e.g. if the build backend does not support this).

+ ** `+-r+`: Include run-time requirements

+ (this flag is not needed and exists for backward-compatibility reasons only,

+ run-time requirements are included by default).

  ** `+-x EXTRA+`: Include dependencies given by the given <<Extras,extra>>.

- Implies `+-r+`.

+ Cannot be used with `+-R+`.

  ** `+-t+`: Include dependencies for the default _tox_ environment.

- Implies `+-r+`.

+ Cannot be used with `+-R+`.

  ** `+-e ENV+`: Include dependencies for the given _tox_ environment,

  and save the `+ENV+` name as `+%{toxenv}+`.

- Implies `+-r+`.

+ Cannot be used with `+-R+`.

  Multiple comma separated values can be given, for example:

  +

  [source,spec]

Looks good to me, as the reporter of the linked Bugzilla issue.

Pull-Request has been merged by churchyard

2 years ago
Metadata