There are some software packages which are not available in the tumbleweed repos. I understand that all distributions universally recommend against installing outside the provided repos. But its unavoidable. They are either impossible or difficult to replace for my use case.
Below is what I anticipate being the order of preference for non-repo installs. Is it correct? Am I missing something?
Overall I would like to have the system package manager at least know about non-OpenSUSE packages existing and ideally look for updates. Is it possible? Some sort of local, custom repo? Or is there some other consolidation strategy?
alternative repos
benefits: still managed by usual system package manager. will find updates.
problems: It seems like there is only a couple and other than the xfce4 repo they don’t have much I am interested in.
rpm
I don’t use this prior so all questions.
Some are available for download as rpms which could be installed with zypper install
. The documentation warns against installing rpms targeted at other distros. Are there generic rpms or should I assume any rpm which does not mention TW is incompatible?
I am also seeing some projects provide instructions on how to build an rpm from source. Is there a benefit to this?
Do yum
, dnf
or other rpm package managers available do anything special/different compared to zypper
so far as 3rd party packages go? Or are they just different ways to interface with the same underlying system?
Is there a way to automatically check for updates for packages installed via rpms, or does it require manual checking and replacing by the user?
language/platform-based package manager
examples: pip/pipx, cargo, npm, basher
benefits: updates can usually be handled by the parent application if you remember to run them.
problems:
In the past when I was running a system with very limited set of packages from the vendor, I relied on a patchwork of such installation methods. It was somewhat functional but really not great for long term use.
source
Everything I want to use can be built/run from source typically obtain from a git repo.
problems: all kinds of dependency issues. You end up with a bunch of dev packages on the system, which can cause conflicts.
Updates must be done manually.
I read Review of the week 2024/08 about python 3.9 deprecation and I wonder what if anything this would mean for pip/pipx packages. Python versions have been a problem on every system I’ve run but the impact varies.
portable formats
And then there is AppImage and flatpak. Have not used them much.
Benefits: IIRC AppImages can check themselves for updates when run.
Problems: Seem to be quite resource intensive.
open build service
I do not understand if this is relevant or not. Documentation for end users is very thin. Using the web interface I searched for packages and don’t find anything extra available here. I mistakenly thought in one instance I did and attempted to add the OBS repo per instruction in the results but the repo was unfindable. Is this active and if so, is there any reason to use it?
A related question
A couple of packages are in the repos, but they do not install due to missing dependencies. How do I handle this?