On Mon, Sep 16, 2019 at 1:44 PM Gergely Polonkai <gergely(a)polonkai.eu>
wrote:
Without any packaging experience, the tar.gz file is not the source,
it is
a compiled version of the software. So iʼd say you should go the hard route
and do the compilation in RPM time.
It is. The tar.gz contains the source, a Makefile that pulls the
dependencies and spits out a binary. Pretty much the equivalent of a C
program that is released as a tarball with a Makefile. I understand that
some (most) C applications also have a configure step, but haproxy never
has and I'm fine with that -- you just prep and build.
However, as far as my Golang-fu goes, you will have a bunch of build
dependencies, but probably zero runtime deps (which is great in one way,
but i personally find a semi-bad idea).
Right. If I treated this as a normal golang application and ignored the
tarball release, I would have to define the dependencies as BuildRequires.
Definitely possible, but since the released tarball does that for me, why
not take advantage of it?
Appreciate the feedback.
Ryan
Best,
Gergely
On Mon, 16 Sep 2019, 18:18 Ryan O'Hara, <rohara(a)redhat.com> wrote:
> I'd like to package a Go application [1] that provides a tarball for each
> stable release. That's great, but it seems that I have two options:
>
> 1. Use the tarball as a source in the spec file, the proceed as usual.
> The Makefile included with this tarball will handle all the Go dependencies.
>
> 2. Treat this as a Go application, avoid the tarball and have the spec
> file define all the BuildRequires.
>
> Thoughts? I've been packaging for ages but this will be my first Golang
> package. One way seems easier but might not be the best way. Cheers.
>
> Ryan
>
> [1]
https://github.com/haproxytech/dataplaneapi
>
>
>
> _______________________________________________
> packaging mailing list -- packaging(a)lists.fedoraproject.org
> To unsubscribe send an email to packaging-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...
>
_______________________________________________
packaging mailing list -- packaging(a)lists.fedoraproject.org
To unsubscribe send an email to packaging-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproje...