Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] webkitgtk: bump to version 2.16.5
Date: Wed, 05 Jul 2017 20:19:33 +0200	[thread overview]
Message-ID: <871spuzqyy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170705200406.GB2822@momiji> (Adrian Perez de Castro's message of "Wed, 5 Jul 2017 20:04:06 +0300")

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

Hi,

 >> Thanks! I've had bumping webkitgtk on my TODO for a while as there old
 >> version is affected by a number of CVEs.

 > You're welcome! I am a WebKit developer myself (mostly working on the GTK+
 > port), and we have been trying that distributions ship WebKitGTK+ updates
 > promptly. At work we use Buildroot now and then, and we were just wondering
 > why an old version was still in use ? so I just went ahead and sent the patch
 > to update, hoping that it would go through :-)

Great, thanks for doing that! Our webkitgtk package could definately use
some love!

 >> I take it that you actively use webkitgtk? I personally don't. Would you
 >> be interested getting added to DEVELOPERS and looking after the package?

 > Sure thing, I can send a patch to add myself. For testing builds I usually
 > target the Raspberry Pi 3, which is what I have around always for testing.
 > Is this enough for me to try builds when making patches, or would you
 > recommend having some other board for development? Everyday WebKit development
 > is done on x86_64, so that's a very well tested target, too.

I think testing on a rpi3 would be fine, thanks.

 > On a different note, I am also considering to submit packages in the following
 > days for the WPE WebKit port [1], which has a focus on embedded and has been
 > recently upstreamed. This will be more than a single patch because the port
 > has graphics back-ends selectable at runtime. Do you think it would be
 > difficult to get those landed?

Sounds great - I don't see any reason why we wouldn't take them,
especially if you would help maintain them.

 > (We have a few downstream forks of Buildroot with build recipes, but they need
 > cleaning up in order to follow the contribution guidelines, and it would be
 > nicer to rebase those on ?master? when/if it gets the WPE packages in :D)

Ok, great!

 > [1] One of my work mates wrote a blog post about it a while ago:
 >     http://blogs.igalia.com/magomez/2016/12/19/wpe-web-platform-for-embedded/

Yes, I saw the blog back then - Nice work!

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-07-05 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 14:33 [Buildroot] [PATCH 1/1] webkitgtk: bump to version 2.16.5 Adrian Perez de Castro
2017-07-05 15:16 ` Peter Korsgaard
2017-07-05 17:04   ` Adrian Perez de Castro
2017-07-05 17:42     ` Adrian Perez de Castro
2017-07-05 18:19     ` Peter Korsgaard [this message]
2017-07-19 14:05 ` Peter Korsgaard
2017-07-20  6:05   ` Peter Korsgaard
2017-07-21 15:23     ` Adrian Perez de Castro
2017-07-21 16:21       ` Peter Korsgaard
2017-07-28 14:09     ` Adrian Perez de Castro
2017-07-29 20:34     ` 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=871spuzqyy.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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