From: Beniamin Sandu <beniaminsandu@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: Re: [meta-oe][PATCH] libtorrent-rasterbar: add initial recipe for 2.0.10
Date: Thu, 11 Apr 2024 22:06:00 +0100 [thread overview]
Message-ID: <CABQJdOHE=fuk9k2jDj6uciqsTfZbQGD=uATD_yFwTsmnwzS0bg@mail.gmail.com> (raw)
In-Reply-To: <20240410223025.318718-1-beniaminsandu@gmail.com>
I see the revert for
https://git.openembedded.org/meta-openembedded/commit/?h=master-next&id=0597c931ffbadf2a2242d8ed9cccb8567953d489
is staged on master-next. Wouldn't this bring us to the previous
situation where the CVE is addressed to the wrong library? I thought
we should map it to the new recipe instead?
On Wed, 10 Apr 2024 at 23:30, Beniamin Sandu <beniaminsandu@gmail.com> wrote:
>
> Signed-off-by: Beniamin Sandu <beniaminsandu@gmail.com>
> ---
> .../libtorrent-rasterbar_2.0.10.bb | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
>
> diff --git a/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb b/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
> new file mode 100644
> index 000000000..084e3c408
> --- /dev/null
> +++ b/meta-oe/recipes-connectivity/libtorrent-rasterbar/libtorrent-rasterbar_2.0.10.bb
> @@ -0,0 +1,31 @@
> +DESCRIPTION = "libtorrent is a feature complete C++ bittorrent implementation \
> + focusing on efficiency and scalability."
> +HOMEPAGE = "https://libtorrent.org/"
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d8b6cb42d66e6b3c47a909c3ce678a7b"
> +
> +DEPENDS = "boost openssl"
> +
> +SRC_URI = "git://github.com/arvidn/libtorrent.git;branch=master;protocol=https \
> + git://github.com/arvidn/try_signal.git;branch=master;protocol=https;destsuffix=git/deps/try_signal;name=try_signal"
> +
> +SRCREV = "74bc93a37a5e31c78f0aa02037a68fb9ac5deb41"
> +SRCREV_try_signal = "105cce59972f925a33aa6b1c3109e4cd3caf583d"
> +SRCREV_FORMAT .= "_try_signal"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit cmake pkgconfig python3targetconfig
> +
> +EXTRA_OECMAKE = "-DCMAKE_BUILD_TYPE=Release"
> +
> +PACKAGECONFIG ??= "python3"
> +PACKAGECONFIG[python3] = "-Dpython-bindings=ON,-Dpython-bindings=OFF,python3-distutils-extra-native"
> +
> +# Strip host paths from autogenerated files
> +do_install:append() {
> + sed -i 's+${STAGING_LIBDIR}+${libdir}+g' ${D}${libdir}/pkgconfig/${BPN}.pc
> +}
> +
> +PACKAGES += "${@bb.utils.contains('PACKAGECONFIG', 'python3', 'python3-${BPN}', '', d)}"
> +FILES:python3-${BPN} = "${PYTHON_SITEPACKAGES_DIR}/*"
> --
> 2.34.1
>
prev parent reply other threads:[~2024-04-11 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 22:30 [meta-oe][PATCH] libtorrent-rasterbar: add initial recipe for 2.0.10 Beniamin Sandu
2024-04-11 21:06 ` Beniamin Sandu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABQJdOHE=fuk9k2jDj6uciqsTfZbQGD=uATD_yFwTsmnwzS0bg@mail.gmail.com' \
--to=beniaminsandu@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).