Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Adrian Perez de Castro <aperez@igalia.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/cog: bump to version 0.18.0
Date: Fri, 8 Sep 2023 21:46:20 +0200	[thread overview]
Message-ID: <20230908214620.0d515173@windsurf> (raw)
In-Reply-To: <20230908192714.2716398-1-james.hilliard1@gmail.com>

On Fri,  8 Sep 2023 13:27:14 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> -COG_VERSION = 0.16.1
> +COG_VERSION = 0.18.0
>  COG_SITE = https://wpewebkit.org/releases
>  COG_SOURCE = cog-$(COG_VERSION).tar.xz
>  COG_INSTALL_STAGING = YES
> @@ -15,7 +15,7 @@ COG_CONF_OPTS = \
>  	-Ddocumentation=false \
>  	-Dmanpages=false \
>  	-Dprograms=true \
> -	-Dsoup2=enabled \

Shouldn't this have been changed to -Dsoup2=disabled as part of commit
dff67170f73959e6826ec3e87e892747f8d3a5fb, which changed wpewebkit to
use libsoup3 instead of libsoup2 ?

I think it makes sense to have this separate from the cog version bump.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-09-08 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 19:27 [Buildroot] [PATCH 1/1] package/cog: bump to version 0.18.0 James Hilliard
2023-09-08 19:46 ` Thomas Petazzoni via buildroot [this message]
2023-09-08 20:58   ` James Hilliard
2023-09-09  6:31     ` Thomas Petazzoni via buildroot
2023-09-09  6:40       ` James Hilliard
2023-09-29 20:05 ` Peter Korsgaard

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=20230908214620.0d515173@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --cc=james.hilliard1@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