Hi,
Dne 27. 10. 20 v 13:52 Martin Curlej napsal(a):
Hi,
EOL and Obsoletes were planned as a feature of Modularity. The feature
should enable to set shorter/longer life cycles on Modules than the OS
release. The initial idea was to set this information in the disgit
metadata of a Module. As time went by the requirements have changed.
From DNF team's perspective, a packaging system is not complete without
Obsoletes. That's why we believe module Obsoletes are a must have to
ensure smooth system upgrades and regular updates on systems consuming
Rawhide (or any other rolling stream). I created a Fedora Change[1]
which got accepted already. We'll deliver support for module Obsoletes
in DNF as soon as possible and we hope it's going to be used in Fedora
34 (or 35 at latest).
The API is clear: DNF expects additional 'modulemd-obsoletes' YAML
documents in modules.yaml. The new document format is getting into
libmodulemd and there's going to be documentation on how to write it.
Then there's a question how to get the documents into modules.yaml. From
my perspective, it's up to Fedora infra/releng/packaging people. Whether
it should be in dist-git, git repo (similar to modulemd-defaults or
comps), PDC, Bodhi (similar to updateinfo) or somewhere else - that's
entirely their call.
[1]
https://fedoraproject.org/w/index.php?title=Changes/Module_Obsoletes_and_EOL
From my point of view right now it seems that this information should
not be a part of the module (disgit, repository metadata). It is prone
to human error when we leave this in the hands of a packager. So this
would need a review of Engineering to be reliable.
Next is that a lot of 3rd parties like to handle the EOL and Obsoletes
of packages/modules by other means, which makes this redundant. Also,
as the release cycle of Fedora is so fast, I am not sure this is a
necessary feature at all
I spoke to people in the community and I got mixed information/opinions,
so I want to open a discussion about this feature. So WDYT? Is this
necessary for Fedora? If yes, how should we handle this?
--
Martin Curlej
Software Engineer, Product Owner
Modularity
Red Hat
<https://www.redhat.com>
mcurlej@xxxxxxxxxx <mailto:mcurlej@xxxxxxxxxx>
<https://red.ht/sig>
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
