On Wed, 29 Jan 2025 at 10:20, Böszörményi Zoltán <zbos...@gmail.com> wrote:
> >> +LICENSE = "LGPL-2.0-or-later & Apache-2.0 & BSL-1.0 & MIT &
> >> Unicode-DFS-2016 & (Apache-2.0 | MIT) & (MIT | Apache-2.0 | Zlib) &
> >> (Unlicense | MIT)"
> > This is very elaborate, how was it determined? How to ensure it remains
> > correct?
>
> It was taken from the Fedora specfile license line verbatim.
> IIRC, they (Red Hat) have a large contingent of lawyers
I guess you could add a recipe comment pointing to the original specfile online.
> > Why can't we use upstream's standard install procedure? Also,
> > cargo.bbclass has an install function, why is it completely replaced?
>
> Because it fails with:
>
> | DEBUG: Python function extend_recipe_sysroot finished
> | DEBUG: Executing shell function do_install
> | ERROR: Did not find anything to install
Yes, cargo_do_install only copies executables, you need to opt into
libraries by setting CARGO_INSTALL_LIBRARIES.
But before that, presumably sequioa upstream has a standard
installation procedure that we can try to use instead of copying files
by hand?
I'm particularly interested in how ${S}/target/release/rpm-sequoia.pc
is supposed to be installed.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#210358):
https://lists.openembedded.org/g/openembedded-core/message/210358
Mute This Topic: https://lists.openembedded.org/mt/110874796/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
