4 ms·

I think I'm going to manually build things from source until Homebrew officially supports M1 and Big Sur. I don't want to deal with any sort of migration / funk

by syas 6y ago

I think I'm going to manually build things from source until Homebrew officially supports M1 and Big Sur. I don't want to deal with any sort of migration / funky re-install, personally.

grey-area 6y ago
Homebrew is just a way of compiling upstream packages. If homebrew is broken building from source will be broken too.
- masklinn 6y ago
  Homebrew distributes prebuilt binary packages. It’s possible that the architecture for this is improperly set up and does not understand that different architectures exist: unlike macports, homebrew was born after the x86 transition. That’s why one user above suggests `-s`: it forces a compilation from source.
  - grey-area 6y ago
    The problems with homebrew packages at present are mostly down to projects like Go and Rust not being updated for M1 ARM yet and hence sources not compiling properly rather than a problem with homebrew itself. So users attempting to compile from original upstream sources would run into similar problems. They have an overview issue here: https://github.com/Homebrew/brew/issues/7857 https://github.com/Homebrew/brew/issues/7857
    - steveklabnik 6y ago
      Rust does have tier 2 support, but it hasn’t made its way to stable yet. This means if you did try in upstream today, it would work.
dewey 6y ago
> I don't want to deal with any sort of migration / funky re-install, personally. Wouldn't this just make things even messier? Some packages from Homebrew and some compiled from source that you have to remember to update manually?
- syas 6y ago
  In the short run yeah. You have a point. I intend to uninstall & reinstall everything once Homebrew is officially supported though, which isn't a big deal for me (and I actually kind of enjoy building from source just for the experience). But these replies are making me think that a large part of my decision to do this is motivated by me just not understanding Homebrew well enough (e.g. how easy it is to nuke everything). Oh well, we'll see how it goes.
jdminhbg 6y ago
> I don't want to deal with any sort of migration / funky re-install, personally. Isn't the benefit of Homebrew that it all goes into /usr/local and it can just blow everything away if necessary? You could run `brew leaves` to see what packages you have, uninstall everything, and reinstall. Easier than keeping track of what you've manually installed where.
acdha 6y ago
That approach has always ended badly in my experience because your manual installs will require more care to remove than the Hombrew ones. My usual recommendation is to install anything which supports it using --HEAD which will keep things tracked and make it trivial to either completely uninstall or simply use "brew reinstall" packages after the upstream stabilizes.

by syas 6y ago

I think I'm going to manually build things from source until Homebrew officially supports M1 and Big Sur. I don't want to deal with any sort of migration / funky re-install, personally.

grey-area 6y ago

Homebrew is just a way of compiling upstream packages. If homebrew is broken building from source will be broken too.

masklinn 6y ago
Homebrew distributes prebuilt binary packages. It’s possible that the architecture for this is improperly set up and does not understand that different architectures exist: unlike macports, homebrew was born after the x86 transition. That’s why one user above suggests `-s`: it forces a compilation from source.
- grey-area 6y ago
  The problems with homebrew packages at present are mostly down to projects like Go and Rust not being updated for M1 ARM yet and hence sources not compiling properly rather than a problem with homebrew itself. So users attempting to compile from original upstream sources would run into similar problems. They have an overview issue here: https://github.com/Homebrew/brew/issues/7857 https://github.com/Homebrew/brew/issues/7857
  - steveklabnik 6y ago
    Rust does have tier 2 support, but it hasn’t made its way to stable yet. This means if you did try in upstream today, it would work.

dewey 6y ago

> I don't want to deal with any sort of migration / funky re-install, personally. Wouldn't this just make things even messier? Some packages from Homebrew and some compiled from source that you have to remember to update manually?

syas 6y ago
In the short run yeah. You have a point. I intend to uninstall & reinstall everything once Homebrew is officially supported though, which isn't a big deal for me (and I actually kind of enjoy building from source just for the experience). But these replies are making me think that a large part of my decision to do this is motivated by me just not understanding Homebrew well enough (e.g. how easy it is to nuke everything). Oh well, we'll see how it goes.

jdminhbg 6y ago

> I don't want to deal with any sort of migration / funky re-install, personally. Isn't the benefit of Homebrew that it all goes into /usr/local and it can just blow everything away if necessary? You could run `brew leaves` to see what packages you have, uninstall everything, and reinstall. Easier than keeping track of what you've manually installed where.

acdha 6y ago

That approach has always ended badly in my experience because your manual installs will require more care to remove than the Hombrew ones. My usual recommendation is to install anything which supports it using --HEAD which will keep things tracked and make it trivial to either completely uninstall or simply use "brew reinstall" packages after the upstream stabilizes.