#389 Add the ability to pass in buildrequire and require overrides on a module build
Merged by lsedlar. Opened by mprahl.
Unknown source master

Download 389.patch

Addresses part of FACTORY-3084

@cqi @jkaluza @ralph could you please review?

rebased onto f116860c6195e5234a3d872f6ba3db8c7a835de5

rebased onto be9e9f2da80da933e03a254179284bd8d7bf8f1e

rebased onto 0e72a3f6b3e6b6e0951b2d82663c601801f655f0

rebased onto c40dbb23211c117d957776f0ac72dbfe85a6cd21

It might be a good idea to disallow certain keys in optional_dict. For example, if optional parameter contains any of these it would cause a confusing behavior: scmurl, branch, buildrequire_overrides, require_overrides.

Good idea. I should probably make this a separate PR though since this problem existed before this PR.

@lucarval, I submitted a PR that should address this:
https://pagure.io/rpkg/pull-request/391

@lsedlar could you please review this as well?

:thumbsup:

A minor suggestion is to validate --buildrequires and --requires values during argparse parses option values. Setting a validation function to argument type parameter.

FYI adding kwargs not at the end is not backwards compatible and would break users that call the method without naming the kwargs. But hey, that does not happen here, so +1 for this more reasonable ordering.

Looks good to me. :thumbsup:

rebased onto 5a054d769be4ebf917e5430d0c440ab449c8738b

rebased onto 93720cbe75b217de25c8ff5546e4f9cd8f855d68

rebased onto 89e34eb68d5a01eb11c09974391b83348850338a

Pull-Request has been merged by lsedlar

Metadata