Firstly, just because it isn’t in the ‘standard’ repos doesn’t mean that there isn’t an easy install for it: That’s not to say that using a hard or harder way of installing is bad, but it may well be unnecessary.
Roughly, in order of ease, easiest first
- install from a standard repo
- add an extra repo with the program that you want in it, and then proceed as if it were in a standard repo
- download the rpm, and put that rpm into you local repo
- build the program from sources
- build the program from sources as an rpm
note that if you have a hundred machines to install on, rather than just one, that will tilt the playing field somewhat, and maybe over the hundred installs something down the bottom of the list turns out to be easier overall, or uses less bandwidth, if that is a critical issue.
Anyway, you probably want to know about this ‘add the repo’ method. You need to know two things;
in which repo the target program can be found
how to add the repo
(my method) use the web at Get it to search for a piece of software and look for the software. You don’t, in my method, use Get It to install the software, just get the repo info, so you copy the link address of the repo.
Go into Yast, install and remove software, repos, configuration add repo (names vary slightly depending on version of Yast); you need to split the repo into two elements, the first part is the machine name and the second is the directory on that machine
Add this repo with a relatively low priority (low priority is equal to a high number, so you can usually use a number of 100 - 120)
Now you can get any package from that repo in the same way as you would with any other package and the install system will keep working in the normal way if that package is updated; ie, you’ll be able to see that an updated version of the program is available when you look for updates in yast.
Note on repo selection; if the package that you want is available in a good general repo like packman, science or education select that rather than a very specific repo, otherwise you will end up adding many repos each of which with one or two packages in it. Well, unless you can only get the version that you need from a very specific repo. (Very specific repos often have someone’s name in them, and are often the work of one enthusiast and are good if you want just the thing that the particular enthusiast is interested in, but are often very narrowly focussed; if that is the only place you can get what you want, add that repo, but if you can get what you want from packman, use that instead.)
(The reason that I don’t go all the way and just use the ‘one click install’ method from ‘Get It’, is that doesn’t give you the control over the priority of the repo, and I’d rather have that control than have to sort it out later, because that can be a bit of a mess, if you have allowed ‘Get It’ to install loads of repos, and you need then to rework it, but YMMV and it is probably tolerable if you only ever add a very small number of extra repos.)