somepackage requires otherpackage version >10.1.79
otherpackage is already at latest version
Have fun compiling it yourself and messing up what is managed by the package manager and what’s not. And don’t forget that the update might break some other package along the way
Most of the time you can just download a release and place the binary in path (or a symlink).
Compiling it yourself should not ‘messing up’ anything, it should build locally:
./configure
make -j$(nproc)
Now it’s just built, nothing on your system has changed. make install will place requisite files where they need to go, but this generally configurable via prefix or equivalent. You may need to install dependencies, but that’s usually a simple exercise in reading the output from the configuration step.
Compiling software is easy as fuck and is incredibly flexible.
Huh, pacman always seemed to automatically work out those dependency loops, or whatever you want to call them, when I was on EndeavourOS. The only time I had an issue with updating was when I went like two weeks without updating, and then ran out of harddrive space halfway through installing the 600 updates.
I’ve been running Bazzite for several months now, and updating is absurdly easy and unintrusive. It’s basically impossible to fuckup (and if you do, it’s extremely simple to rollback). I can really see immutable/atomic being the future of Linux.
Don’t use apostrophes wherever you see an “s” at the end of a word. If you’re unsure about whether or not to use an apostrophe, just don’t. Because statistically, there are far fewer cases where you need 'em than there are cases where you don’t. Plus if you missed the apostrophe where it should be, people will just assume you didn’t bother to type it or it was a typo. Whereas if you do type it where it shouldn’t be, it’s a clear case of “this person doesn’t know how apostrophes work”.
Have fun compiling it yourself and messing up what is managed by the package manager and what’s not. And don’t forget that the update might break some other package along the way
Most of the time you can just download a release and place the binary in path (or a symlink).
Compiling it yourself should not ‘messing up’ anything, it should build locally:
Now it’s just built, nothing on your system has changed.
make installwill place requisite files where they need to go, but this generally configurable viaprefixor equivalent. You may need to install dependencies, but that’s usually a simple exercise in reading the output from the configuration step.Compiling software is easy as fuck and is incredibly flexible.
Huh, pacman always seemed to automatically work out those dependency loops, or whatever you want to call them, when I was on EndeavourOS. The only time I had an issue with updating was when I went like two weeks without updating, and then ran out of harddrive space halfway through installing the 600 updates.
I’ve been running Bazzite for several months now, and updating is absurdly easy and unintrusive. It’s basically impossible to fuckup (and if you do, it’s extremely simple to rollback). I can really see immutable/atomic being the future of Linux.
If your distro maintainer’s do a good job, that situation never happen’s.
Or just use gentoo where that problem doensn’t exist at all.
Don’t use apostrophes wherever you see an “s” at the end of a word. If you’re unsure about whether or not to use an apostrophe, just don’t. Because statistically, there are far fewer cases where you need 'em than there are cases where you don’t. Plus if you missed the apostrophe where it should be, people will just assume you didn’t bother to type it or it was a typo. Whereas if you do type it where it shouldn’t be, it’s a clear case of “this person doesn’t know how apostrophes work”.
Shut’s the’s fuck’s up’s.
Manjaro, is that you?