Yup…all 17 pages. Not all the links though! I did read the initial article though. Being fairly new to linux (coming from windows) I have trouble getting into some of the terms used. I have a vague idea of what a ‘dependency’ is, but I’m not sure. I think a ‘dependency’ is a functionality you need to have in order to run a certain program. Like ‘OpenGL’ is a dependency for fx OpenArena. Is this correct? Searching for ‘dependencies’ in the wiki didn’t seem to provide any links to the actual meaning of the word in linux context.
More importantly I’d like to know more about the 4 repos policy. I don’t fully understand the problem its meant to address. Is it the programs in the other repos or the repos themselves that is the problem? I often find myself looking for native games to install. Most of those I look at are not in the 4 repos. I’d be nice to know if I could install a game from a non-recommended repo, and then remove the repo again afterwards, if that would address the problem. Or if I should just keep my paws away.
> I often find myself looking for native games to install. Most of those I
> look at are not in the 4 repos. I’d be nice to know if I could install a
> game from a non-recommended repo, and then remove the repo again
> afterwards, if that would address the problem. Or if I should just keep
> my paws away.
it is always a good idea to ask before doing something which leads to
trouble and you do that. So I appreciate your question. I think there are
different opinions around about the usage of repos. The repo you refer to
are the games repos from the build service I guess.
You do not need to “keep your paws away” just need to be aware that
sometimes an additional repo can contain the same packages but slightly
different (e. g. different version) as the main repos. So adding
repositories without care can lead to a hell of conflicts or “funny” side
What you mentioned is always the best solution: If you realy want something
from an obs repository which is not elsewhere available (or misses
functionality) add the repo during the install (1-click does that) and make
sure that it is removed after the installation (this is NOT default with 1-
click so look at the screens coming up during the install there is a
checkbox to remove it after install or if you miss that remove it manually
The installed software will of course still work but you have some evidence
not to add something by accident which replaces important packages with
something which conflicts.
It is not that the obs builds are “evil” it is only that they can be a
source of problems/conflicts if one is not carefull.
Dependency is the kind of dependency from the rpm system (the package
management) which is the base for what zypper and yast are doing, I can not
realy explain that short or have a good link, maybe someone else.
openSUSE 11.2 64 bit | Intel Core2 Quad Q8300@2.50GHz | Gnome 2.28 | GeForce
9600 GT | 4GB Ram
openSUSE 11.3 64 bit | Intel Core2 Duo T9300@2.50GHz | Gnome 2.30 | Quadro
FX 3600M | 4GB Ram
Sometimes it may make sense just to keep the “not main” repository but to set the priority low (means to a higher number).
This could be done under: yast2 (YaST Control Center)> Software > Software Repositories
I have set the priorities of my repositories like that:
oss - 99
non-oss - 99
updates - 99
printing - 99 (cause I trust the new hplip for my HP All-In-One mehr more)
GNOME 2.28 Stable - 100 (I got the 2.28.3 power manager from there - had problems with the old one)
packman - 110
videolan - 115
some ‘private’ repository - 120
But if you like you could differentiate even more (or better) - surely there will be further remarks…
Just to clarify the “clarification” and “conferment”:
“priority low (means to a higher number)” is equivalent to “lower the number means a higher priority”.
But if you set the priority of the main (to be preferred) repositories higher (e. g. to 50) than the standard priority (99):
that may have the advantage that a new repositories has a lower priority just when it is added (half) automatically.