On Sat, Nov 17, 2018, at 12:24 PM, Jonathan Dieter wrote: > Agreed, that this would be a massive format change and should therefore > be a major version bump for RPM. New versions of RPM should still be > able to read and install old-format rpms, but, as you point out, old > versions of RPM won't be able to read or install new-format rpms. > Unfortunately, I don't see any way around this. After having introduced a new format (OSTree) into the ecosystem here, as well as working a lot on the Docker/OCI ecosystem, one thing I want to emphasize is: A lot of Red Hat's customers don't connect their systems to the Internet, they want easy offline mirroring. OSTree supports that, and it's also possible to do with OCI images of course. But, a lot organizations use e.g. https://jfrog.com/artifactory/ which today doesn't support OSTree (it does support RPM and Docker/OCI). So any format break for RPM wouldn't be usable until Artifactory gains support for it. And even after that happened you'd have in some places a large lag time for it to be deployed. In general, any data format break is going to impose a lot higher costs than you might imagine. (Also on this topic, I should note that the OSTree data format cleanly fixes a lot of the issues being discussed here; it has deltas, and also doesn't make the mistake of checksumming compressed data, when performing updates only changed files are rewritten, not to mention a whole transactional update system, etc.) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
