On 31. 03. 20 16:39, Ladislav Slezak wrote:
Dne 31. 03. 20 v 8:59 Jiri Srain napsal(a):
It is even worse: The self-update is not limited to YaST packages (you can update any part of inst-sys). There the version scheme will fail (unless you introduce way more logic).
We could check only some specific YaST packages.
(Actually that's already implemented in the existing downgrade check, we compare the versions only for some white-listed YaST packages, we do not care about the others.)
If you work this idea a bit further, this is perhaps something that could also work with the quarterly re-spins (you could distinguish which package should apply to which quarterly release even if they are all in the same repository).
Yes, but you would need to add it to *every* package, even to non-YaST packages, that would be a bit more difficult to enforce...
Or not. You could turn this Provides into an API to the maintenance team telling them that the update is supposed to go to a self-update :-) This would be something for longer discussion with maintenance, though. Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Krizikova 148/34 tel: +420 284 084 659 186 00 Praha 8 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org