Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libwpe: switch back to version 1.14.2
Date: Thu, 25 Jan 2024 22:11:39 +0100	[thread overview]
Message-ID: <8734ul6ruc.fsf@48ers.dk> (raw)
In-Reply-To: <20240125144121.1534299-1-aperez@igalia.com> (Adrian Perez de Castro's message of "Thu, 25 Jan 2024 16:41:17 +0200")

>>>>> "Adrian" == Adrian Perez de Castro <aperez@igalia.com> writes:

 > The versioning scheme for libwpe uses the middle version number to
 > indicate stability: an even number for stable releases, odd for
 > development preview releases. As such, Buildroot should be using
 > version 1.14.2, which is the most recent of the stable releases.
 > While at it, add a note in the .mk file about the versioning scheme.

Hmm, this was bumped back in July before 2023.08-rc1. Is there no 1.16.x
version coming?

 > Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
 > ---
 >  package/libwpe/libwpe.hash | 6 +++---
 >  package/libwpe/libwpe.mk   | 3 ++-
 >  2 files changed, 5 insertions(+), 4 deletions(-)

 > diff --git a/package/libwpe/libwpe.hash b/package/libwpe/libwpe.hash
 > index 226b4f3295..554b1f2b0e 100644
 > --- a/package/libwpe/libwpe.hash
 > +++ b/package/libwpe/libwpe.hash
 > @@ -1,6 +1,6 @@
 > -# From https://wpewebkit.org/releases/libwpe-1.15.1.tar.xz.sums
 > -sha1  0082ceb475175bfecd1172f2c0b292824d31561b  libwpe-1.15.1.tar.xz
 > -sha256  14d36a93a05ab7ada9bec581720b8057336fe681bbbe59bda7d50cb8f3eba3a6  libwpe-1.15.1.tar.xz
 > +# From https://wpewebkit.org/releases/libwpe-1.14.2.tar.xz.sums
 > +sha1  70a2b894af2b50d7082260158a89524974a480f3  libwpe-1.14.2.tar.xz
 > +sha256  8ae38022c50cb340c96fdbee1217f1e46ab57fbc1c8ba98142565abbedbe22ef  libwpe-1.14.2.tar.xz
 
 >  # Hashes for license files:
 >  sha256  35bef295cedbbf179eaee14328002587a0e7dc08ebf3f15ea080a6f2815f0d7b  COPYING
 > diff --git a/package/libwpe/libwpe.mk b/package/libwpe/libwpe.mk
 > index f8c6b0fc76..1fbdd5fcc3 100644
 > --- a/package/libwpe/libwpe.mk
 > +++ b/package/libwpe/libwpe.mk
 > @@ -4,7 +4,8 @@
 >  #
 >  ################################################################################
 
 > -LIBWPE_VERSION = 1.15.1
 > +# The middle number is even for stable releases, odd for development ones.
 > +LIBWPE_VERSION = 1.14.2
 >  LIBWPE_SITE = https://wpewebkit.org/releases
 >  LIBWPE_SOURCE = libwpe-$(LIBWPE_VERSION).tar.xz
 >  LIBWPE_INSTALL_STAGING = YES
 > -- 

 > 2.43.0

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


-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-01-25 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 14:41 [Buildroot] [PATCH] package/libwpe: switch back to version 1.14.2 Adrian Perez de Castro
2024-01-25 21:11 ` Peter Korsgaard [this message]
2024-01-25 22:33   ` Adrian Perez de Castro
2024-01-26  8:43     ` Peter Korsgaard
2024-01-31  8:26       ` Adrian Perez de Castro

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=8734ul6ruc.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=aperez@igalia.com \
    --cc=buildroot@buildroot.org \
    /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