nim reported a new issue against the project: `golist` that you are following: `` This is a similar issue to https://pagure.io/golist/issue/3 this time for packagers that try to package several import paths in a single spec (I’m told the practice is common RHEL-side).
For this use pattern to work reliably, you need to compute the codebase requirements in a single pass. Otherwise `golist` will forget to filter out imports of code, already available on-system under another import path. And that will break BuildRequires computation.
So we need something like
```sh $ golist --imported --skip-self --with-tests --package-path %{goipath0} --package-path %{goipath1} --package-path %{goipath2} ``` ``
To reply, visit the link below or just reply to this email https://pagure.io/golist/issue/4
qulogic added a new comment to an issue you are following: `` I think most of the code is already written to handle this; it just needs to fix the CLI flags to work correctly. ``
To reply, visit the link below or just reply to this email https://pagure.io/golist/issue/4
The issue: `golist needs to be able to process multiple import paths in one pass` of project: `golist` has been assigned to `qulogic` by qulogic.
qulogic added a new comment to an issue you are following: `` Fixed by #22. ``
To reply, visit the link below or just reply to this email https://pagure.io/golist/issue/4
The status of the issue: `golist needs to be able to process multiple import paths in one pass` of project: `golist` has been updated to: Closed by qulogic.
golang@lists.fedoraproject.org
-
Elliott Sales de Andrade -
Nicolas Mailhot