Dne 20. 03. 20 v 16:07 Ladislav Slezak napsal(a):
3. Custom provides flag
We could possibly use some custom RPM flag, something like "Provides:
yast-self-update-version(15.2)" added when releasing a self-update. We could
compare it with the value stored in the /etc/os-release file in the inst-sys.
Because it's enough to have this flag only once in the self-update repository we
would add it just to the first YaST package released as a self-update. The other
package updates released later would not need to have this flag.
I deliberately selected the "15.2" value which corresponds to the "VERSION_ID"
tag in the /etc/os-release file because this is the same for both SLE-15-SP2 and
Leap 15.2 so we could easily build the same self-update packages also for Leap
15.2 if needed.
4. Additional "Conflicts" flag
This would be similar to the previous solution, but instead of custom "Provides"
we could use more logical "Conflicts" dependency. This would also avoid using
some
non-standard "Provides" tag.
For example when releasing a new "yast2-installation" self-update we would
add "Conflicts: yast2 < 4.2.78" (or whatever version would be released in the
SP2 GM).
Then the self-update code would evaluate all conflict dependencies of the
updated
packages and report an error if some conflict is found.
Advantages:
- more logical
- no special tag
Disadvantages:
- if the repository contains no YaST package yet we cannot easily add this
conflict
to the other packages (but sooner or later there will be an YaST update so
this
is rather a theoretical or short term problem)
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
