On 26/09/2019 17.55, H.Merijn Brand wrote:
On Thu, 26 Sep 2019 16:17:29 +0100, Peter Suetterlin <pit@astro.su.se> wrote:
Carlos E. R. wrote:
On 25/09/2019 17.20, Peter Suetterlin wrote:
H.Merijn Brand wrote: [...]
Manually added rpms usually have a different vendor, and as such are not touched without notification. 'zypper up' doesn't change vendor, nor does 'zypper dup' in TW (now).
Problem is, when the notification comes, one doesn't remember that this particular package should not be changed. YaST/Zypper do not allow to add our comments to repos.
Well, the topic was manually installed RPMs. I don't count those from other repos as 'manual install'
Oh, but I do!
Of course they are.
There is a plethora of very useful repositories available for almost every recent version of openSUSE, but it is strongly advised *against* adding all the repositories as active repositories, as that can lead to conflicts or installation of packages that might be harmful somehow.
So I find a piece of software that I want or need and choose the repo I most trust. If this is the *only* package on the repo, I add the repo, use zypper to install the package and then disable the repo. If my work on a certain machine requires me to have that product up-to-date I do not disable it.
After installation, any "zypper dup" call would suggest to remove it
Manual additions include software I (regret to) require for work. e.g.: zoom, skype, teamviewer, DbSchema, SQL Developer, and MS SQL Server.
Others include stuff I really like, but I cannot find in repositories (which can change any day of course) or are commercial: crossover, spotify, dbeaver
Some include commercial rpm's for which (by now) repositories exist, but those cannot be updated as that specific version is required for the environment they are used in, e.g. oracle-*.rpm: Instant Client 12.1 is extremely different from 19.3
Then there are packages for which I needed a different version than currently available to get a plugin or other tool working: I want to make useful backups for my Android phone, and home:ahjolinna offers just what I want, but it requires other packages from that repo that conflict with my current TW installation. I just pick what I absolutely need without causing conflicts. To me that is manual installation, but it comes from a repo. IIRC it required wine-mono newer than I have.
Yes. One method would be to create a local directory as repo, and put all those package there. Routinely run a zypper dup from that repo as verification that all is Ok. And have a text file in it explaining where each package there comes from, and why it is there.
An example:
I have Lazarus from the pascal repo. I open YaST, select packman repo, and slect "switch system packages to this repo".
TBH, I've never ever used that command, especially for that reason....
It is documented in the wiki and other places, almost as a mandatory step after installing openSUSE.
So, I have to do things in this order, and remember it:
Playing Memory or Sudoku regularly might help making the remembering part easier *veg*
But having the tools to remember it for you is so much easier, isn't it?
That is what we use computers for. To automate things.
That can e an issue, sort of, in several ways. If you really do a 'make install' that causes lots of issues, if it is intended to *replace* software that is required in the package system. So /usr/local is not a good choice in that case, nor is /opt. The system has to know somehow the software is there, even though there is no package.
/usr/local is the correct place for make install, it is the purpose of that tree.
Yes, of course. But it's bad to do this if you intend to *replace* required system parts. Not because of the location per se, but because it's not known to the package system....
That might indeed be handy in some cases. You might circumvent this by creating a pattern that has that package as requirement?
Not something an admin can do. Only a dev.
I've never done it, but it should just be creating an rpm with needed dependencies. Try rpm -ql patterns-base-minimal_base rpm -q --requires patterns-base-minimal_base
and likely
zypper si patterns-base
to learn how the spec file looks
Oh, I know how they look. They look Very complicated.
I will for sure try to create my own repo locally and add that. This discussion showed at least a few cases where that would be useful
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)