Exa: Release new version to GitHub?

[elliottsj]

Is the latest code on master suitable for a new release? I'd like to install the latest version through brew cask to avoid the malloc_zone_unregister issue (#121). Thanks!

[elliottsj]

I'm also wondering whether it would be ideal to move exa from homebrew-cask over to homebrew-core. From my understanding, this would allow us to do something like brew install exa --HEAD to install the latest version from source.

[iKevinY]

Good call! I was the one who originally wrote the formula for exa; at that time, there were pretty much no other Rust-build core formulae, so I just wrote it as a homebrew-cask formula instead.

I have a core-compatible formula ready to go if you want to push a new release, @ogham!

[sethvoltz]

@iKevinY Mind sharing for those of us who want to do it anyway?

[iKevinY]

The Homebrew folks don't accept HEAD-only formulae anymore, so I have to wait for a new stable release of exa before submitting the formula to Homebrew's core. In the mean time, it's probably easier to just install it via cargo install --git https://github.com/ogham/exa.

[MoritzFago]

I too have the issue #121 after I installed exa via home-brew cask. How should I proceed. Also for home-brew core vs cask: core allows automatic updates via brew, as cask is afaik only for install and not for updating, it foists this off to the autoupdaters, which usually come with GUI software, for whom cask was made. Just my 2 cents.

[iKevinY]

@MoritzFago If you install Rust using either Homebrew or rustup, it should include Cargo, which means you can run the command in my comment above to install exa directly from the master branch of this repository (which fixes that issue).

[iKevinY]

Given the circumstances, I think I'm going to fork exa strictly for the purpose of publishing a new release, and then work on updating the Homebrew formula to point to this release. This seems better than simply leaving a broken release up. To clarify, I won't be forking exa to maintain further development, but rather simply to get Homebrew installation working again.

For some additional context, I sent an email to @ogham about a month ago regarding pushing a new release, and he hasn't replied; I'd be more than happy to close my fork if development resumes.

[ogham]

I created a release (accompanied by a short novella) here: https://github.com/ogham/exa/releases/tag/v0.4.1

[iKevinY]

@ogham Glad to see you're doing alright! I totally empathize with your situation — it's only natural for motivation and interests to shift, and sometimes it's best to simply take a break.

Thank you for creating this new release; I'll go and update my Homebrew PRs! 😄

[elliottsj]

@ogham Great to hear back from you. I really appreciate your courage writing about your motivation trouble in the release notes. Every developer has to take a break from time to time, especially in open source. I know I've had trouble motivating myself over the past little while too; so you're not alone ❤️

I'm sure I speak for all exa users when I say that no one thinks poorly of you or thinks you made a mistake by not replying to bug threads. I, for one, am happy that you created exa, no matter how much of your time you decide to dedicate to help maintain the project 😄

I would love to start contributing more to exa as soon as I get the opportunity; learning rust has been something I wanted to do for a while now. I'm setting myself a reminder to look through other issues in this repo to help triage them.

[vitorgalvao]

This issue can now be closed. exa is now a formula instead of a cask.

[elliottsj]

Link for the lazy: https://github.com/Homebrew/homebrew-core/pull/11817