fucking hate installer scripts when you can just do the same with packages

@miekg Recently I opened for myself mise(https://mise.jdx.dev/). Ii use it mostly for project-level tools management. But additionally to that I’ve started to use it for global tools installation. It can download binaries from GitHub releases, npm, etc.
It also supports a post install commands, to configure something if needed.

It won’t replace installation script for homebrew, but vast majority of tools are good to go.

P.S. I don’t enjoy go install, npm install, etc.

Home | mise-en-place

mise-en-place documentation

mise-en-place
@safigo use go install for one-off go binary installs into ~/bin, otherwise packages!
@miekg it true, unless I miss something, homebrew/pacman and mise will be more preferable way for me due to improved version management.
Go mod works really well for a project’s dependency management, but for global installs it feels not good enough.
@safigo but on a linux machine I need dpkg to tell me all versions, not some 3rd party thing. Not in the least for compliance

@miekg hard to disagree, somehow I thought you meant some “go get” packages or so. It’s why I’ve chosen #Arch, its packages include almost everything, no PPAs, etc. Very convenient to have almost everything in an official repository.

If something is available only by PPA, I’d prefer to choose mise as well. It does not add more dependencies to your distribution for simpler upgrade and newer versions will be available as soon as GitHub release is created with binaries.

The deep down idea is to not worry anymore about PPAs and have everything installed in a user space (no root access).

@safigo eyeing arch for a while now... But doing Deb based distro since 1996

@miekg Oh... I feel you are an expert there :)

My path have started from gentoo with emerge with later various distro hops, like OpenSuse Ubuntu Mint Debian, etc.

But deep dive Gentoo I liked the most, since it had the least issues with packages. The reason I've never came back there, is a compilation time.
I remember how I built KDE for more than 20 hours (Celeron 2.4 in early 2000s).

After many years in MacOS (right now it's also a primary OS, Arch is only on a big PC), it's really confusing that many things are not available without hacks.
In MacOS Homebrew made it so simple, it's hard to accept that Linux may have so many complications with a package distributions.

It looks like snap or flatpack should fix this issue, but they don't. Many things from snap don't work or do not available, flatpack the same.

Installing Homebrew in Linux does not feel right.

#gentoo #emerge #opensuse #ubuntu #mint #debian #macos #homebrew #snap #flatpack

@safigo @miekg IMHO gentoo worst part (except deps. Conflict) requirements to have build tools in system (gcc, rust, golang, nodejs) even if you don’t use it and that’s only one step in build for Firefox ¯\_(ツ)_/¯

@gordio @miekg Yeah.... all of that increases a compilation time.

When I used it, there were no NodeJS, Golang, Rust, etc. and software was simpler in general. At the same time hardware was slower.

It's hard to say what is better... But 20+ hours is 20+ hours

@safigo @miekg true.
In the past, I only hated Boost. 😅
@gordio @miekg Not only compilation, but interface as well
@gordio @safigo @miekg Every System has tradeoffs. #gentoo skews toward customizability and it seems that's not what you want. Btw binhost will ease setup time considerably when running a "conventional" system.

@ftranschel @gordio @miekg don't take it negatively, Gentoo is an amazing distro.
The discussion was more about nostalgia.

Currently I've chosen Arch, it looks like a better fit for me right now.

I remember, when I built Gentoo with tuning gcc parameters for my CPU and optimized Linux kernel, I did it not just for fun. My PC felt much faster with all those optimizations. KDE felt laggy without those steps.

But nostalgia works differently for me. It's just really fun to remember how I left my pc overnight to finish compilation. Using lynx to access the website with instructions (there were no phones and tablets with browsers).

@ftranschel @gordio @miekg about binhost, I remember at some point I figured out I’m not ready to compile everything anymore. I proceeded to compile only things that affect my continuous OS usage: kernel, utils, libraries, KDE, Firefox. But OpenOffice I started to download precompiled.
Maybe something else as well, but OpenOffice was too huge.

It seems that in early 2000 binhost already existed, or at least some tools had recompiled options.