hi,
I'm on f22 and have consul and etcd from the repos
ldd /usr/bin/consul linux-vdso.so.1 (0x00007ffc98fa2000) liblmdb.so.0.0.0 => /lib64/liblmdb.so.0.0.0 (0x00007f99bc1b5000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f99bbf99000) libc.so.6 => /lib64/libc.so.6 (0x00007f99bbbd8000) /lib64/ld-linux-x86-64.so.2 (0x0000562f58dbf000)
ldd /usr/bin/etcd not a dynamic executable
I found that when CGO_ENABLED=0 it would be statically linked the dynamic one like consul above is not actually dynamically linked (because of the size)
are there some fedora guidelines for golang apps? are there macros and helpers for rpm?
On 10/30/2015 10:07 PM, Muayyad AlSadi wrote:
hi,
I'm on f22 and have consul and etcd from the repos
ldd /usr/bin/consul linux-vdso.so.1 (0x00007ffc98fa2000) liblmdb.so.0.0.0 => /lib64/liblmdb.so.0.0.0 (0x00007f99bc1b5000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f99bbf99000) libc.so.6 => /lib64/libc.so.6 (0x00007f99bbbd8000) /lib64/ld-linux-x86-64.so.2 (0x0000562f58dbf000)
ldd /usr/bin/etcd not a dynamic executable
I found that when CGO_ENABLED=0 it would be statically linked the dynamic one like consul above is not actually dynamically linked (because of the size)
are there some fedora guidelines for golang apps? are there macros and helpers for rpm?
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?
This needs help in going from a draft to real guidelines.
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?
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.
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.
Adam
----- Original Message -----
From: "Adam Goode" adam@spicenitz.org To: devel@lists.fedoraproject.org Cc: "Matthew Miller" mattdm@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?
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.
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.
Jakub
Adam
devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Fri, Nov 06, 2015 at 10:11:08AM -0500, Jakub Cajka wrote:
----- Original Message -----
From: "Adam Goode" <adam at spicenitz.org> To: devel at lists.fedoraproject.org Cc: "Matthew Miller" <mattdm at 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?
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
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/ ...
On Sun, Nov 8, 2015 at 5:35 AM, Adam Goode adam@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> To: devel at lists.fedoraproject.org Cc: "Matthew Miller" <mattdm at 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?
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 https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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 <adam@spicenitz.org mailto:adam@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
On Mon, Nov 16, 2015 at 10:28 AM, Jan Chaloupka jchaloup@redhat.com wrote:
*.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?
sources = source tarballs = tarball with source codes
or I'm mistaken.
On 11/16/2015 11:10 AM, Muayyad AlSadi wrote:
On Mon, Nov 16, 2015 at 10:28 AM, Jan Chaloupka <jchaloup@redhat.com mailto:jchaloup@redhat.com> wrote:
*.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?
sources = source tarballs = tarball with source codes
or I'm mistaken.
Yes, sources contains a list of tarballs that are used to build an rpm. However, each tarball can contain more than just source codes.