On 11/13/2015 12:15 PM, Muayyad AlSadi wrote:
> At this time, Go libraries packaged in Fedora are primarily for the
purpose of being BuildRequires for building Fedora binary RPMs,
since golang is like statically linked and does not prefer .so for
libraries (so far). I suggest never package BuildRequires RPMs for
golang (I think of it like .a libraries)
and for the offline building of golang binaries like etcd we might
collect dependencies in a way similar to python wheel and include them
in the .src.rpm
%build
tar -xzf %SOURCE2 -C golang-path/
...
*.src.rpm is reserved for a spec file, sources and patches. It does not
provide any tarball with source codes. Or am I missing something?
Currently, all source codes are shipped in a form of NAME-devel.rpm
which I see as a libraries whose packages you import in golang project
(although they are all pure source codes).
On Sun, Nov 8, 2015 at 5:35 AM, Adam Goode <a...@spicenitz.org
<mailto:a...@spicenitz.org>> wrote:
On Fri, Nov 06, 2015 at 10:11:08AM -0500, Jakub Cajka wrote:
> ----- Original Message -----
> > From: "Adam Goode" <adam at spicenitz.org <http://spicenitz.org>>
> > To: devel at lists.fedoraproject.org
<http://lists.fedoraproject.org>
> > Cc: "Matthew Miller" <mattdm at fedoraproject.org
<http://fedoraproject.org>>
> > Sent: Friday, November 6, 2015 3:47:42 PM
> > Subject: Re: packaging golang guidelines (like etcd, consul)
> >
> > On Mon, Nov 02, 2015 at 09:05:09AM -0500, Matthew Miller wrote:
> > > On Sun, Nov 01, 2015 at 05:44:42PM +0100, Jan Chaloupka wrote:
> > > > >are there some fedora guidelines for golang apps?
> > > > >are there macros and helpers for rpm?
> > > > https://fedoraproject.org/wiki/PackagingDrafts/Go
> > >
> > > This needs help in going from a draft to real guidelines.
> > >
> >
> > I am also trying to figure this out. Looking at actual
> > packaged golang things in Fedora, I see quite a difference
> > between the drafts and what I see in specfiles. There
> > are a lot of macros copied everywhere.
> >
>
> Could you please elaborate.
>
I figured it out. The generated packages are all from gofed.
They all share a lot of generated macros and comments.
> >
> > Is there any more up to date guidance? It would be an
> > improvement to even just copy/paste emails of discussions
> > into the bottom of the wiki draft.
> >
>
> This(https://fedoraproject.org/wiki/PackagingDrafts/Go)
> should be most up to date. For discussion see FPC ticket
> https://fedorahosted.org/fpc/ticket/382.
>
> Any input will be welcomed.
When I was looking to make the specfile, I jumped right to the
section in the wiki with the sample. I missed gofed completely.
I will add a note to the wiki suggesting to try gofed repo2spec
first before trying one of the sample specfiles in the page.
>
> Jakub
>
> >
> >
> > Adam
Thanks for the help!
Adam
--
devel mailing list
devel@lists.fedoraproject.org <mailto:devel@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
