qulogic opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Use --with-tests when running checks also.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/20
atodorov opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
macros: Accept options for %gotest
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/23
blowry opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Remove tildes from goname
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/26
berrange opened a new pull-request against the project: `go-rpm-macros` that you are following:
``
Expose Go build flags directly to spec files as a macro
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/pull-request/21
Hi all,
I'm currently working on packaging github.com/writeas/writefreely, a platform for building writing spaces. Some of its dependencies are currently not packaged for Fedora, so I'm seeking some advice on the granularity to which I should be packaging each dependency. I initially wrote this email to packaging(a)lists.fedoraproject.org, and I got directed here, so apologies if you're in both lists.
github.com/writeas/writefreely depends on github.com/writeas/web-core. This is a library that is used by the project developers (write.as) for all their shared code. It is likely that this will be used as a dependency for future packages (for example, when their photo sharing service, snap.as, gets released), but unlikely that it will ever be used by anyone other than these developers.
Therefore, should github.com/writeas/web-core be its own package, should I bundle it in with writefreely, should it be a subpackage of writefreely, or indeed something else?
Additionally, web-core has its own dependencies of the same kind. Where possible, I have submitted PRs[1,2,3] to their repo to reduce unnecessary dependencies, but web-core still depends upon github.com/writeas/impart and github.com/writeas/openssl-go. These libraries are both unlikely to be used anywhere else; should these be bundled too?
If the correct course of action is to bundle the dependencies (in a nested way), I would really appreciate somebody experienced at packaging Go packages to give some guidance on how to do this sensibly with the Go SPEC file macro system. This is especially since the current documentation[4] seems pretty light on the topic of dealing with SPEC files with multiple sources.
Also, this is my first time joining a mailing list to actually get involved with the Fedora project, so do let me know if this sort of question actually belongs elsewhere.
Kind regards,
Edd Salkield
[1] https://github.com/writeas/web-core/pull/6
[2] https://github.com/writeas/web-core/pull/8
[3] https://github.com/writeas/web-core/pull/10
[4] https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/
proletarius101 reported a new issue against the project: `go-rpm-macros` that you are following:
``
Although go-rpm-macros haven't support Go modules, which bascially means no lockfile & always use the latest deps available in Fedora's repo, it might be good to provide some macro to (imperfectly) handle some easy problems introduced by Go modules.
One of them is that when a module uses `replace` keyword to substitute module with another goipath (e.g. `replace golang.org/x/crypto => github.com/ProtonMail/crypto` in https://github.com/emersion/hydroxide/blob/master/go.mod). My proposal is to replace the `golang.org/x/crypto` with its real path `github.com/ProtonMail/crypto`. But any other ideas will be welcomed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/go-rpm-macros/issue/27