Add brew and apt support

[dbalatero]

Hi @reese, hope you're good! Wondering if there are plans to add this as a Cargo package so you can cargo install rubyfmt?

I have a few other linting plugins that work that way that I use from Neovim (example), and they seem to nicely make their way to my $PATH without much more work. Thanks!

[reese]

I feel like we should have a better distribution strategy, but I don't think any plans are set at the moment. (cc @penelopezone if you've got thoughts on this.)

My first thought is that having to actually build the Ruby checkout might make something like cargo install kinda annoying unless we got rid of all of the build-time system dependencies (like make and autoreconf). It might end up being more straightforward to have precompiled binaries and to use system package managers like brew instead, but I definitely think having some kind of easier package management is something we should do.

[dbalatero]

I think brew install rubyfmt / apt-get install rubyfmt would be totally fine ways to distribute it. I'm thinking of integrating it into my company's pipeline, and I really just need a cheap, no-nonsense way to:

• get it into CI pipelines
• get it onto dev machines

Honestly, the package manager approach would probably be most familiar to folks, and cargo would be a bit more niche unless you do Rust!

[fables-tales]

Strong 👍 we should do brew and apt but not cargo

[matthewford]

brew fails if you run make release

bash -c "find target/release | grep -i 'librubyfmt-.*\.a' | xargs rm; exit 0"
find: target/release: No such file or directory

[reese]

@matthewford how is brew involved here? What's the original command you're running?

[matthewford]

@reese my recipe is here: https://github.com/matthewford/homebrew-core/tree/bump-rubyfmt-0.8

I don't think it's a brew issue specifically I see there was an old closed issue with the same error

[matthewford]

#340

[matthewford]

Homebrew/homebrew-core#88103 (comment) this is the same issue

[matthewford]

@reese using your homebew PR I see a similar issue:

Last 15 lines from /Users/matthewford/Library/Logs/Homebrew/rubyfmt/01.cargo:
   Compiling rubyfmt v0.8.0-pre (/private/tmp/rubyfmt-20221120-87784-1mvjnl7/rubyfmt-0.8.0/librubyfmt)
   Compiling unicode-normalization v0.1.21
   Compiling addr2line v0.17.0
   Compiling aho-corasick v0.7.18
   Compiling object v0.29.0
   Compiling bstr v0.2.17
error: failed to run custom build command for `rubyfmt v0.8.0-pre (/private/tmp/rubyfmt-20221120-87784-1mvjnl7/rubyfmt-0.8.0/librubyfmt)`

Caused by:
  process didn't exit successfully: `/private/tmp/rubyfmt-20221120-87784-1mvjnl7/rubyfmt-0.8.0/target/release/build/rubyfmt-072919fc54932cda/build-script-build` (exit status: 1)
  --- stderr
  fatal: not a git repository (or any of the parent directories): .git
  Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
warning: build failed, waiting for other jobs to finish...
error: failed to compile `rubyfmt-main v0.8.0-pre (/private/tmp/rubyfmt-20221120-87784-1mvjnl7/rubyfmt-0.8.0)`, intermediate artifacts can be found at `/private/tmp/rubyfmt-20221120-87784-1mvjnl7/rubyfmt-0.8.0/target`

[reese]

I think you're pointing to several different issues here, the issue on my PR, #340, and the make error you're referring to are all separate issues.

[reese]

Mine is because we rely on a git checkout, so we probably need to actually pull the submodule first, your error is because make release calls find which exits non-zero the first time you build

[reese]

#340 is specific to M1 and is referring to an error in the build script, that's separate from either of these

[matthewford]

@reese I got around the it's not a git dir, by cloning in this commit matthewford/homebrew-core@649219c, but then ran into the other issue about find: target/release: No such file or directory. Not on an M1 mac

[reese]

Right, I'm saying the M1 bit is not what you're running into. You can either just mkdir_p "target/release" or just use cargo install like on my PR instead. (Are you committing to doing the brew bit here? I'm happy to leave this to you if you want, we don't need to both be working on this)