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.
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.
NixOS solved this. You can install both deps from two different channels.