packaging guidelines draft

[Matthew Miller]

Hi everyone. Let's get https://fedoraproject.org/wiki/PackagingDrafts/Go
polished up and out of draft form.

One thing I'm wondering about is dependency generation. Right now, we have a
standard for BuildRequires which uses the import path, like

BuildRequires: golang(github.com/gorilla/context)

This side of things can't really be scripted (although we could provide a
helper tool to look for them -- the same tool could warn about embedded
third-party libs), but should we look at adding a find-provides script for
the other side? It would be nice to reduce the amount of complexity inthe
spec files.

Maybe we could also have a macro for the BuildArch? Right now, that's
somewhat complicated, using noarch on Fedora and RHEL 7 but (due to PPC)
ExclusiveArch on other EPEL.

[Peter Lemenkov]

Hello All!

2013/10/21 Matthew Miller :
> Hi everyone. Let's get https://fedoraproject.org/wiki/PackagingDrafts/Go
> polished up and out of draft form.
>
> One thing I'm wondering about is dependency generation. Right now, we have a
> standard for BuildRequires which uses the import path, like
>
> BuildRequires: golang(github.com/gorilla/context)
>
> This side of things can't really be scripted (although we could provide a
> helper tool to look for them -- the same tool could warn about embedded
> third-party libs), but should we look at adding a find-provides script for
> the other side? It would be nice to reduce the amount of complexity inthe
> spec files.
>
> Maybe we could also have a macro for the BuildArch? Right now, that's
> somewhat complicated, using noarch on Fedora and RHEL 7 but (due to PPC)
> ExclusiveArch on other EPEL.

I'd like to add that we have pseudo-user "golang-sig" now. (S)he has
accounts in both Bugzilla and Koji, so please next time anoyne
packages anothe golang application please add him/her to InitialCC
list.

Also we have now GMane mirror for this list!

* http://dir.gmane.org/gmane.linux.redhat.fedora.golang

More news to come - stay tuned!