You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most popular package system for OS X is Homebrew.
I highly recommend that you create a brew formula/recipe for IPFS as per https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Formula-Cookbook.md and register it with brew or one of the taps. Then you can install a binary file and have go and git as dependencies, and if someone is using a non-supported Mac OS version or GO version it will compile them instead.
With this formula everything can be installed by:
brew tap ipfs/ipfs (required until you are approved to be in the master index)
I had stayed away because i read they did not want alpha things. But if setting up our own tap is fine, let's do that. for repo name in the org, i think ipfs/brew-tap.
we can also have all the other little tools (multihash, multiaddr, iptb, graphmd, ...) published on there.
Binary distribution is unwanted
hmm it's annoying to force users to compile things... particularly if the deps are non trivial. any idea why this is? is this purely a security concern? or is there something else?
hmm it's annoying to force users to compile things... particularly if the deps are non trivial. any idea why this is? is this purely a security concern? or is there something else?
Never found the official reason - they pre build (I think, their term is bottling) popular packages though. Maybe it's a complication/security/reproducibility thing?
After reading the docs I think ipfs/homebrew-ipfs or ipfs/homebrew-tap would be better. As far as I understood it has to begin with homebrew-…
hmm it's annoying to force users to compile things... particularly if the deps are non trivial. any idea why this is? is this purely a security concern? or is there something else?
I think as long as we don't want to get into the main homebrew repo we can do binary distribution as they don't check the taps for compliance to their rules… I think most (or all?) of the main repo is pre-built for the main OS versions / configurations and there are just "bottles" to install… (Their own binary distribution)
As I understand it if you do your own tap, you can do binary, and you can set some dependencies so if there is a new version of OSX released it will compile instead of using binary.
That being said, compile with brew is pretty fast and easy.
I think ipfs/homebrew-ipfs or ipfs/homebrew-tap would be better.
👍 is ipfs/homebrew-ipfs-tap overkill? whatever is most clear to users who ever see the repo name only. ipfs/homebrew-ipfs may be enough.
Okay, let's try their way (compile) for now until we run into issues. once we have our own signed binaries we can revisit the question if relevant. (maybe even provide checksums of binaries to check, if the builds are reproducible, etc).
I think thats our bad, we forgot to change the in code version before bumping the tag number. so it may be building at tag 0.3.5
Yup. that's the case. The version bump in code came some commits after the tag.
@jbenet it looks like they track both the revision hash and the tag name. I'm not sure what happens when you reassign the tag but I'd expect an error when they don't match.
Personally, I'd wait for 0.4 before we bump brew again.
Activity
Luzifer commentedon Apr 27, 2015
All following points are regarding the official Homebrew repo:
(Refs: Acceptable Formulae)
As long as we set up an own tap this should be okay and for the users there is only one additional command to add a tap…
jbenet commentedon Apr 27, 2015
👍 thanks @ChristopherA and @Luzifer
I had stayed away because i read they did not want alpha things. But if setting up our own tap is fine, let's do that. for repo name in the org, i think
ipfs/brew-tap.we can also have all the other little tools (
multihash,multiaddr,iptb,graphmd, ...) published on there.hmm it's annoying to force users to compile things... particularly if the deps are non trivial. any idea why this is? is this purely a security concern? or is there something else?
cryptix commentedon Apr 27, 2015
Never found the official reason - they pre build (I think, their term is bottling) popular packages though. Maybe it's a complication/security/reproducibility thing?
Luzifer commentedon Apr 27, 2015
After reading the docs I think
ipfs/homebrew-ipfsoripfs/homebrew-tapwould be better. As far as I understood it has to begin withhomebrew-…I think as long as we don't want to get into the main homebrew repo we can do binary distribution as they don't check the taps for compliance to their rules… I think most (or all?) of the main repo is pre-built for the main OS versions / configurations and there are just "bottles" to install… (Their own binary distribution)
ChristopherA commentedon Apr 27, 2015
As I understand it if you do your own tap, you can do binary, and you can set some dependencies so if there is a new version of OSX released it will compile instead of using binary.
That being said, compile with brew is pretty fast and easy.
jbenet commentedon Apr 27, 2015
👍 is
ipfs/homebrew-ipfs-tapoverkill? whatever is most clear to users who ever see the repo name only.ipfs/homebrew-ipfsmay be enough.Okay, let's try their way (compile) for now until we run into issues. once we have our own signed binaries we can revisit the question if relevant. (maybe even provide checksums of binaries to check, if the builds are reproducible, etc).
Luzifer commentedon Jul 6, 2015
Someone created a formula and submitted it but:
Version 0.3.5 should identify as 0.3.5, not as 0.3.4
whyrusleeping commentedon Jul 6, 2015
I think thats our bad, we forgot to change the in code version before bumping the tag number. so it may be building at tag 0.3.5
jbenet commentedon Jul 7, 2015
@whyrusleeping we should update the tag then? do we know if this is kosher with
brew?cryptix commentedon Jul 7, 2015
Yup. that's the case. The version bump in code came some commits after the tag.
@jbenet it looks like they track both the revision hash and the tag name. I'm not sure what happens when you reassign the tag but I'd expect an error when they don't match.
Personally, I'd wait for 0.4 before we bump brew again.
whyrusleeping commentedon Jul 7, 2015
0.4 is gonna be great.
daviddias commentedon Jan 2, 2016
Let's keep track of this on the distributions repo ipfs/distributions#22