From: Adrian Perez de Castro <aperez@igalia.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libwpe: switch back to version 1.14.2
Date: Wed, 31 Jan 2024 10:26:12 +0200 [thread overview]
Message-ID: <20240131102612.GD4009850@igalia.com> (raw)
In-Reply-To: <43b543a2-6782-42f2-ac09-1c72d9c49d59@korsgaard.com>
[-- Attachment #1.1: Type: text/plain, Size: 1770 bytes --]
On Fri, 26 Jan 2024 09:43:23 +0100 Peter Korsgaard <peter@korsgaard.com> wrote:
> On 25/01/2024 23.33, Adrian Perez de Castro wrote:
> >> Hmm, this was bumped back in July before 2023.08-rc1. Is there no 1.16.x
> >> version coming?
> >
> > Not anytime soon. Release 1.14.2 which I just made yesterday includes all the
> > fixes that are also in 1.15.2 -- usually we only do a new stable branch if
> > there are new features, and we haven't added anything to libwpe for a quite
> > long time.
> >
> > Also, Yann asked on IRC whether the packages that depend on libwpe
> > (wpebackend-fdo, wpewebkit, gst1-plugins-bad) can use 1.14.x... Yes,
> > they can. For WPE WebKit we even have a compatibility table here:
> >
> > https://wpewebkit.org/release/schedule/
> >
> > =)
>
> OK, good - Applied, thanks.
Super :)
> > Maybe we should reconsider the versioning scheme, using suffixes for
> > development releases and release candidates ("X.Y-devN", "X-Y-rcN")
> > instead of even/odd numbering. It seems to cause enough confusion to
> > at least consider the change.
>
> I don't really feel strongly about it. It is a bit "odd", but consistent
> with the gtk/gnome stuff.
GNOME has been slowly trying to phase out the even/odd numbering scheme, but
it is true that most libraries are still using it, and so far it has been
mostly user-facing applications the ones that have adopted the new versioning
scheme [1].
Given it's not really a "problem", we actually prefer to avoid changing it
in the WebKit components to avoid churn. What I'll do is add a comment next
to the version string in the .mk files, like I did in this patch, next time
I update the other packages.
Cheers,
—Adrián
---
[1] https://discourse.gnome.org/t/new-gnome-versioning-scheme/4235
[-- 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
prev parent reply other threads:[~2024-01-31 8:26 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
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 [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=20240131102612.GD4009850@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.