Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Thomas Devoogdt <thomas.devoogdt@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/libsoup: add choice between libsoup2 and libsoup3
Date: Mon, 31 Jan 2022 00:02:21 +0200	[thread overview]
Message-ID: <20220131000221.GC987440@momiji> (raw)
In-Reply-To: <20220130154908.0ff0f0b6@windsurf>


[-- Attachment #1.1: Type: text/plain, Size: 1616 bytes --]

Hi Thomas, Thomas, and all,

On Sun, 30 Jan 2022 15:49:08 +0100 Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
 
> Thanks for your patch.
> 
> On Sat, 29 Jan 2022 22:42:35 +0100
> Thomas Devoogdt <thomas.devoogdt@gmail.com> wrote:
> 
> > Libsoup3 has a new API [1], packages using libsoup2 may not
> > compile with libsoup3 or may crash at runtime in unexpected
> > ways. So the default will (for now) stay on libsoup2.
> > A tracking table for the migration can be found here [2].
> 
> A "choice" is not going to work well, as it means that in a given
> configuration we will only be able to install either packages that need
> libsoup2 *or* packages that libsoup3, bit not a mix of both.
> 
> Is it possible to install both libsoup2 and libsoup3 side-by-side in
> the same system? This requires them having a different library name and
> a different location for header files.

Yes, libsoup2 and libsoup3 are parallel-installable, both can coexist in
the same system. The only caveat is, as I mentioned in a previous email,
that having both versions loaded in the same process will result in odd
crashes and assorted failures due to symbols clashing.


> If that's the case, we will definitely want to have a separate libsoup3
> package, so that we can install libsoup and libsoup3 side by side in
> the same system.

Yes, I think we may need to have a separate libsoup2 package. While most
“big” packages are already supporting libsoup3 (or will soon), probably
others (like gupnp) may take longer and allowing to continue building them
with libsoup2 would be a good ide.

Cheers,
—Adrián

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-30 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 21:42 [Buildroot] [PATCH 1/2] package/libglib2: bump version to 2.70.0 Thomas Devoogdt
2022-01-29 21:42 ` [Buildroot] [PATCH 2/2] package/libsoup: add choice between libsoup2 and libsoup3 Thomas Devoogdt
2022-01-30 14:49   ` Thomas Petazzoni via buildroot
2022-01-30 22:02     ` Adrian Perez de Castro [this message]
2022-01-30 22:17       ` Thomas Petazzoni via buildroot
2022-01-31 11:37         ` Thomas Devoogdt
2022-08-21 18:45   ` Yann E. MORIN
2022-01-30 14:52 ` [Buildroot] [PATCH 1/2] package/libglib2: bump version to 2.70.0 Thomas Petazzoni via buildroot
2022-01-31 16:16   ` Thomas Devoogdt
2022-01-31 16:40     ` Fabrice Fontaine

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=20220131000221.GC987440@momiji \
    --to=aperez@igalia.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.devoogdt@gmail.com \
    --cc=thomas.petazzoni@bootlin.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