4 ms·

Couple of `git` points: why are you committing binaries to your master branch? Personally, I also won't be moving anything from a random git repo into /usr/loca

• stephencelis 13y ago
  For those that are worried, the source is there to inspect and compile. For those that aren't, there's reduced friction. It's a young project and I could move the binary elsewhere, but I'm not sure that would change your concern? Is there an alternate process you would suggest?
  • jewel 13y ago
    I believe GP was saying two separate things. First of all, it's unusual to commit binaries to source control, because they can't be merged, etc. Second of all, he personally isn't comfortable with binaries and would rather compile from source. It'd be more traditional to release binaries separately, maybe using the following: https://github.com/blog/1547-release-your-software https://github.com/blog/1547-release-your-software
    • stephencelis 13y ago
      Ah, I'd missed that update. Thanks! I prefer this to the current workflow.
    • alexchamberlain 13y ago
      Indeed, thanks for clarifying. The linked post sounds like a good workflow.
• coldtea 13y ago
  >Personally, I also won't be moving anything from a random git repo into /usr/local/bin... How is a random developer page offering an app download any better?