I have found on the page a piece of information on installing (unstable) version of KDE Plasma 5.7.
On the page there are links to so called repository (http).
My question is about more general aspect of software installation.
As in the above example, how one can install a piece of software having just an access (http link) to a repository?
When you realy need extra repos, the most important can be found by using:
YaST > Software > Repository Management. Then Use Add (lower left). In the next screen select Community Repositories. There you can select for adding repos that are mostly used, the most important being Packman.
Another route would be by using https://software.opensuse.org/search.
When you find some package there, you can use tthe One Click Install. During this a repo will be added. The advice is to disable this repo immedialtly after (also using YaST > Software > Repository Management), to avoid installing libraries by incident from it that are also on e.g. the OSS repo and thus not of the correct version.
When you then think/know that an uodate to the particular software from that repo is available and needed, you can temporary Enable it.
The general advice is to have as few repos as possible. And from those have as few enabled as possible. When you can live with OSS, non-OSS, Update, Update-OSS and Packman, that would be the most stable situation, but many people have some more for e.g. a newer KDE version or special needs like Geo or Education.
But … it would mean you have no access to the dependencies if these are in the same repo.
If you add a repo, the content of that repo is made known to your system.
One wonderful place to start with is the OpenSUSE Documentation.
I always look at it first. This section will help: [Managing Software with Command Line Tools](Managing Software with Command Line Tools)
But if you don’t like the console way, the One Click Install feature will definitively help.
I thank you all of you.
I adore this statement:
**Anything that can go wrong… will teach us
**
That is the best way to learn - on the errors of others. I can assure you, you can count on me!
PS
Just to be certain (if any assurance here is even possible). In order to install any software having its URL repository:
I tend to not mess with repository too much. If the app is not in the official’s one I just download it (mostly from software.opensuse.org and when it doesn’t have much dependencies) and install it, using
I have the strong idea thatyou are still messing things up.
1)
Many software packages reside in so called repositories. When you have such a repositorie (which has an URL) in your repository list (and enabled), you can directly install packages from it by using the package name. You can use zypper and/or YaST > Software for this. When the package you want to install needs other packages for it’s full functionality (so called dependencies), they will also be installed by zypper/YaST, which is of course only possible when these are in one of the repositories in your list of enabled repos. In short, to add a rpo:
zypper ar <URL of repository> <alias>
and to install a package
zypper in <package name>
You can also install individual RPMs. Those RPMs can be either a file on your system, in which case you use the file name, or they can be on another system, in which case you can use it’s URL. This is independent from the fact if that URL is pointing to an RPM that is in a repo or not. It is just the URL of the RPM. When insalling an RPM, just that is done. No dependent packages will be installed. Thus:
zypper in <path/to/the/file.rpm>
or
zypper in <URL of RPM>
The first method above is the “normal” way people here install software. When using the second method (e.g. becaue the RPM is not offered in a repo, but as single RPM), you may detect from several earlier posts, that people then prefer NOT to use the URL directly, but they prefer to download the RPM and then install
from the copy on their system.
The second method also has the drawback that not only are dependent packages not installed automatic, they may even not be available, or, when found somewhere. of the wrong version.
