On Sat, Oct 7, 2017, at 01:26 PM, Stephen John Smoogen wrote: > At a certain point, if you want/need to do these things, it is better > to burn it from the ground and come up with a new packaging system > (and relearn all the second system problems involved with that). I actually put code behind my words here - rpm-ostree today has these semantics (a lot like "yum/dnf distro-sync") by default. This does also imply that everything else that references a version number in e.g. %triggerin are buggy. I looked through most of those a while ago and found that most of them were workarounds for traditional inplace upgrade bugs, which are unneccssary for rpm-ostree. (Of course it also has fully transactional upgrades, an anti-hysteresis model, etc.) It's the same old RPMs, interpreted in a new way. So not a new packaging system, but it definitely fixes this bug. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
