Re: [gentoo-dev] git checkout in ebuild?
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: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 recent grpc API incompatibility. I can successfully compile by going: > > > > go get ... > > cd > > git checkout 1.3.0 > > make all > > > > This gets me the binaries (snaptel, snapteld); does anyone know if I can > > put this process (git checkout..) into an .ebuild file (or some other > > suggestion)? > > > > Cheers, > > emerge -va app-portage/eclass-manpages > man 5 git-r3.eclass > > -> ECLASS_VARIABLES > > Look at almost any ebuild in tree using git-r3.eclass with a - > version for examples of how you can use this if the eclass > documentation isn't clear enough. > > But, these are forbidden in gentoo as a normal package. > > Typically, the solution there is finding a tarball, or producing > a snapshot of the tree and publishing it somewhere. > > There's writing on that here: > > https://devmanual.gentoo.org/ebuild-writing/functions/src_ > unpack/svn-sources/index.html > > and > > https://devmanual.gentoo.org/ebuild-writing/functions/src_ > unpack/cvs-sources/index.html > > But there's no specific reference for Git sources, although the general > rules and concepts still apply. > > Other commenters have mentioned using github tagged release's for > tarballs, but even those aren't necessarily great, because: > > - Historically, the tarball's SHA1 can change due to github's tooling > changing > - Tags are not in any way immutable, and its been seen that people > forcibly replace tags in order to keep their git history tidy. > ( Which doesn't change the functional source code, bug can be > sufficient to change timestamps in the tarball, and thus, the SHA1 ) > >
Re: [gentoo-dev] git checkout in ebuild?
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 recent grpc API incompatibility. I can successfully compile by going: > > go get ... > cd > git checkout 1.3.0 > make all > > This gets me the binaries (snaptel, snapteld); does anyone know if I can > put this process (git checkout..) into an .ebuild file (or some other > suggestion)? > > Cheers, emerge -va app-portage/eclass-manpages man 5 git-r3.eclass -> ECLASS_VARIABLES Look at almost any ebuild in tree using git-r3.eclass with a - version for examples of how you can use this if the eclass documentation isn't clear enough. But, these are forbidden in gentoo as a normal package. Typically, the solution there is finding a tarball, or producing a snapshot of the tree and publishing it somewhere. There's writing on that here: https://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/svn-sources/index.html and https://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html But there's no specific reference for Git sources, although the general rules and concepts still apply. Other commenters have mentioned using github tagged release's for tarballs, but even those aren't necessarily great, because: - Historically, the tarball's SHA1 can change due to github's tooling changing - Tags are not in any way immutable, and its been seen that people forcibly replace tags in order to keep their git history tidy. ( Which doesn't change the functional source code, bug can be sufficient to change timestamps in the tarball, and thus, the SHA1 ) pgpAn2Jhu66aJ.pgp Description: OpenPGP digital signature
Re: [gentoo-dev] git checkout in ebuild?
В письме от понедельник, 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.
Re: [gentoo-dev] git checkout in ebuild?
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:00 :
> 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). 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:
>
> go get ...
>
> cd
>
> git checkout 1.3.0
>
> make all
>
> This gets me the binaries (snaptel, snapteld); does anyone know if I can
> put this process (git
> checkout..) into an .ebuild file (or some other suggestion)?
>
> Cheers,
>
>
> Hi,
>
> You can use git-r3.eclass and use a specific tag or commit.
> See examples on the tree :
> https://github.com/gentoo/gentoo/search?utf8=%E2%9C%93&;
> q=EGIT_COMMIT+git-r3&type=
>
> Best regards,
> --
> Corentin “Nado” Pazdera
>
--
>From Siberia with Love!
Re: [gentoo-dev] git checkout in ebuild?
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 with some type of recent grpc API incompatibility. I can successfully compile by going: go get ... cd git checkout 1.3.0 make all This gets me the binaries (snaptel, snapteld); does anyone know if I can put this process (git checkout..) into an .ebuild file (or some other suggestion)? Cheers, Hi, You can use git-r3.eclass and use a specific tag or commit. See examples on the tree : https://github.com/gentoo/gentoo/search?utf8=%E2%9C%93&q=EGIT_COMMIT+git-r3&type= (https://github.com/gentoo/gentoo/search?utf8=%E2%9C%93&q=EGIT_COMMIT+git-r3&type=) Best regards, -- Corentin “Nado” Pazdera
[gentoo-dev] git checkout in ebuild?
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: go get ... cd git checkout 1.3.0 make all This gets me the binaries (snaptel, snapteld); does anyone know if I can put this process (git checkout..) into an .ebuild file (or some other suggestion)? Cheers,
