Skip to content

Create Brew Formula and tap #1144

Closed
Closed

Description

@ChristopherA

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)
  • brew install ipfs

-- Christopher Allen

Activity

  1. Luzifer commented on Apr 27, 2015

    @Luzifer
    Member

    All following points are regarding the official Homebrew repo:

    • Binary distribution is unwanted
    • Only stable software is accepted

    (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…

  2. jbenet commented on Apr 27, 2015

    @jbenet
    Member

    👍 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.

    • 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?

  3. cryptix commented on Apr 27, 2015

    @cryptix
    Contributor

    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?

  4. Luzifer commented on Apr 27, 2015

    @Luzifer
    Member

    for repo name in the org, i think ipfs/brew-tap.

    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)

  5. ChristopherA commented on Apr 27, 2015

    @ChristopherA
    Author

    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.

  6. jbenet commented on Apr 27, 2015

    @jbenet
    Member

    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).

  7. Luzifer commented on Jul 6, 2015

    @Luzifer
    Member

    Someone created a formula and submitted it but:

    [13:57] luzifer ~> which ipfs
    /usr/local/bin/ipfs
    [13:57] luzifer ~> ls -lh /usr/local/bin/ipfs
    lrwxr-xr-x  1 luzifer  admin    29B  6 Jul 13:56 /usr/local/bin/ipfs -> ../Cellar/ipfs/0.3.5/bin/ipfs
    [13:57] luzifer ~> ipfs version
    ipfs version 0.3.4
    [13:57] luzifer ~>
    

    Version 0.3.5 should identify as 0.3.5, not as 0.3.4

  8. whyrusleeping commented on Jul 6, 2015

    @whyrusleeping
    Member

    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

  9. jbenet commented on Jul 7, 2015

    @jbenet
    Member

    @whyrusleeping we should update the tag then? do we know if this is kosher with brew?

  10. cryptix commented on Jul 7, 2015

    @cryptix
    Contributor

    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.

  11. whyrusleeping commented on Jul 7, 2015

    @whyrusleeping
    Member

    0.4 is gonna be great.

  12. daviddias commented on Jan 2, 2016

    @daviddias
    Member

    Let's keep track of this on the distributions repo ipfs/distributions#22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions