https://bugzilla.redhat.com/show_bug.cgi?id=1301143
--- Comment #9 from Jan Chaloupka <jchaloup(a)redhat.com> ---
Some of them are already packaged, just with a different name.
should this binary have a golang(...)-like name resolvable via
golang(...)
macro?
No. golang(...) virtual provides is used only for dependencies
I've read golang binaries can be named without golang-github-*
prefix so
this won't suffer from renaming
Yeap. It can be named anyway you wish. All projects packaged in fedora with
intent to provide at least one binary are named by repository. The standard way
is to use project name.
(also this do not provide a devel package)
As I mentioned above. At least you can provide devel package with no
[Build]Requires for sake of analysis. The generated spec file already provides
all code necessary. Just with some small modifications.
but just let me know and I'll move the repository as fast as I
can
and fix what's needed
If you use generated macros, it is two-liner fix
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component