The git.r3 eclass method seems good practice for a specific commit. I'll
have a look at the snap site today (AEST) - see if I can find a tarball -
this seems preferable to commit.Thanks for the very helpful replies;
On Tue, Oct 17, 2017 at 8:04 AM, Kent Fredric wrote:
> On Mon, 16 Oct 2017 13:31
On Mon, 16 Oct 2017 13:31:53 +1000
Damo Brisbane wrote:
> Hello,
>
> I am wanting to make an ebuild for Intel's (Apache 2 licensed) snap
> monitoring framework (https://github.com/intelsdi-x/snap). It seems the
> current version (2.0.0) does not compile the golang binaries with some type
> of re
В письме от понедельник, 16 октября 2017 г. 13:42:05 +07 пользователь Azamat
Hackimov написал:
> Github creates tarballs for tags automatically, for 1.3.0 tag it would be
There is go eclasses for that, and I guess OP wanted advice about some go-
eclasses magic for that.
Github creates tarballs for tags automatically, for 1.3.0 tag it would be
https://github.com/intelsdi-x/snap/archive/1.3.0.tar.gz, so you don't need
to use git eclass.
SRC_URI would look like:
SRC_URI="https://github.com/intelsdi-x/snap/archive/${PV}.tar.gz ->
${P}.tar.gz"
2017-10-16 11:13 GMT+05
October 16, 2017 5:30 AM, "Damo Brisbane" wrote:
Hello,
I am wanting to make an ebuild for Intel's (Apache 2 licensed) snap monitoring
framework
(https://github.com/intelsdi-x/snap (https://github.com/intelsdi-x/snap)). It
seems the current version (2.0.0) does not compile the
golang binaries
Hello,
I am wanting to make an ebuild for Intel's (Apache 2 licensed) snap
monitoring framework (https://github.com/intelsdi-x/snap). It seems the
current version (2.0.0) does not compile the golang binaries with some type
of recent grpc API incompatibility. I can successfully compile by going:
g
