On Thu, Oct 20, 2022 at 11:03 AM Miro HronĨok <mhroncok(a)redhat.com> wrote:
On 10. 10. 22 16:32, Ben Cotton wrote:
> For the last 20 years or so, RPM has used a home-grown OpenPGP parser
> for dealing with keys and signatures. That parser is rather infamous
> for its limitations and flaws, and especially in recent years has
> proven a significant burden to RPM development. In order to improve
> security and free developer resources for dealing with RPM's "core
> business" instead, RPM upstream is in the process of deprecating the
> internal parser in favor of [
https://sequoia-pgp.org/ Sequoia PGP]
> based solution written in Rust.
> At this point the change is mostly invisible in normal daily use.
Which of the following will happen:
1) rpm will gain ExclusiveArch: %{rust_arches}
2) we will stop requiring the above in Rust packages, as Rust is 100% available
3) rpm will %ifarch %{rust_arches} this change
4) something else (what?)
IMHO if we do 1) we could as well do 2) because without rpm, we won't be able
to build rpms. 3) seems somewhat tedious for no good reason.
I think 2) would be the easiest solution in the long term. rustc and
LLVM now already support all targets that we *might* want to add in
the near-to-mid-future (riscv64gc-unknown-linux-gnu comes to mind -
its support is at the same level as other targets we already have).
Fabio