https://ipfs.io/ https://github.com/ipfs/go-ipfs/releases IPFS is a decentralized torrent-like networking system with transparent file adding/downloading
Hello, do you wish to proxy maintain this?
I am a Gentoo developer applicant willing to proxy maintain go-ipfs and go-ipfs-bin. Are you willing to mentor me, preferably via mail and IRC?
The official documentation for go-ipfs states in the INSTALL SECTION: Download Go 1.5.2+. Go 1.6 is not yet supported. # eix dev-lang/go [I] dev-lang/go Available versions: 1.6-r2(0/1.6){tbz2} 1.6.1(0/1.6.1){tbz2} (~)1.6.2(0/1.6.2){tbz2} **9999(0/9999) {gccgo} They do however distribute binaries.
Created attachment 433240 [details] go-ipfs-bin-0.4.1.ebuild
Hello bacce, I'm not a developer so I cannot mentor you. Please check the proxy maintainers page: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Just by checking the ebuild, it seems fine, have you tested on x86/amd64/arm?
I am testing on amd64 with keywords set to ~amd64.
@bacce, the Gentoo Proxy-Maintainers are always hanging out in IRC .. details in the link above, on Freenode. Swing by, and meet the team!
KEYWORDS="~amd64 ~x86 ~arm" This means you have run tested this ebuild on all three systems yes? You appear to have proveded a tarball to each arch purely because they are there. They need be run tested before they can be keyworded. Have not seen you in the channel as yet.
I mentioned this inchannel One can submit a package initially eith keywords of arches on which you have tested. Beyond that, it you really want to see the package support the other arches, simply make keyword requests accordingly.
Created attachment 434592 [details] go-ipfs-bin-0.4.1.ebuild with only run-tested arches Same ebuild just with all arches commented out that I have not run-tested.
Created attachment 434594 [details] go-ipfs-bin-0.4.1.ebuild with only run-tested arches *sigh* Its a good thing to also remove the keywords when commenting out the untested arches... *sigh*
Created attachment 434682 [details] go-ipfs-bin-0.4.1.ebuild I've run-tested this in an x86 chroot keyworded to ~x86. Also, fuse really is only RDEPEND since this is a bin-dist ebuild.
Created attachment 434684 [details] go-ipfs-bin-0.4.1.ebuild I as a maintainer suggest +fuse by default.
Created attachment 434686 [details] add QA_PREBUILT
commit 08a3e7653ec7b7dc612a55d15053ccb888f0e441 Author: Sam Jorna <wraeth@gentoo.org> Date: Thu May 19 20:03:49 2016 +1000 net-p2p/go-ipfs-bin: new package IPFS is a decentralized torrent-like networking system with transparent file adding/downloading. Ebuild submitted by new proxied maintainer through bug. Gentoo-bug: 579768 Package-Manager: portage-2.3.0_rc1
Created attachment 434714 [details] go-ipfs-bin-0.4.1.ebuild - excluding all known-to-not-work arches thx @Coacher for review and @tajjada for advice
commit 83a44b756c53ef656b26691324fff901c44c38f4 Author: Sam Jorna <wraeth@gentoo.org> Date: Thu May 19 23:43:03 2016 +1000 net-p2p/go-ipfs-bin: restrict KEYWORDS for binary-only package Restricts the KEYWORDS to arches for which a binary package is available. Reported-by: Coacher <itumaykin+gentoo@gmail.com> Package-Manager: portage-2.3.0_rc1
Just updating bug summary to fall within search.
(In reply to bacce from comment #3) > The official documentation for go-ipfs states in the INSTALL SECTION: > > Download Go 1.5.2+. Go 1.6 is not yet supported. > > # eix dev-lang/go > [I] dev-lang/go > Available versions: 1.6-r2(0/1.6){tbz2} 1.6.1(0/1.6.1){tbz2} > (~)1.6.2(0/1.6.2){tbz2} **9999(0/9999) {gccgo} > > They do however distribute binaries. It's been a few months, and the docs now say it needs Go 1.7+ to build which is in tree. The actual build process sounds like an eldritch horror though — it has its own package manager which grabs files from random other languages' PMs and the ipfs network itself — so I won't complain if 0.4.3 only appears as a -bin package.
Package is in-tree and maintainership has been reassigned. Closing this bug. Thanks for the contributions.
