Hello all,

I started working on rpm 4.19 update, and quickly ran into new,
difficult dependencies: rpm has deprecated its internal crypto
management, and now defaults to external Sequoia library:

https://fedoraproject.org/wiki/Changes/RpmSequoia

Alas, this library is written in rust, and one of its crates wants
libclang as well. While we can delay the inevitable, for now (by
forcing the usage of the deprecated internal crypto, which will
certainly be removed upstream in the future), we also need to consider
what are the long term options:

- move clang into core, and accept that both that, and rust-native are
going to be required for do_package.

- consider that we may need a divorce from the rpm ecosystem. We don't
have a particularly well-established relationship with them, and have
no influence on their roadmap and goals. So maybe we should mark rpm
package format as deprecated, do what we can to ship it in the next
LTS release, and then just remove all of it, and default to ipk. Any
interested party can set up meta-rpm then and maintain it.

Thoughts?

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1856): 
https://lists.openembedded.org/g/openembedded-architecture/message/1856
Mute This Topic: https://lists.openembedded.org/mt/102780086/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to