From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] WebkitGtk upgradation
Date: Thu, 28 Feb 2013 08:36:46 -0300 [thread overview]
Message-ID: <512F414E.5090203@zacarias.com.ar> (raw)
In-Reply-To: <20130228122855.6ceb26ce@skate>
On 02/28/2013 08:28 AM, Thomas Petazzoni wrote:
> My feeling is also that the DirectFB backend of Gtk has never been
> seriously maintained over time. There are from time to time some people
> who fix the issues, but then it goes on unmaintained for a number of
> months/years, during which it slowly degrades into an unusable state.
>
> I would therefore suggest that Buildroot follows upstream: get rid of
> the DirectFB backend. If anyone really wants the DirectFB backend in
> Gtk, then it should be fixed upstream. But I don't think it should
> force Buildroot users to stay with old Webkit/Gtk because of this.
+1
Our current webkit-gtk has more CVEs than spots on a dalmatian dog.
Regards.
next prev parent reply other threads:[~2013-02-28 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 5:53 [Buildroot] WebkitGtk upgradation Bhupal Singh
2013-02-28 7:45 ` Stephan Hoffmann
2013-02-28 8:52 ` Bhupal Singh
2013-02-28 10:22 ` Will Newton
2013-02-28 11:28 ` Thomas Petazzoni
2013-02-28 11:36 ` Gustavo Zacarias [this message]
2013-02-28 12:23 ` Peter Korsgaard
2013-03-06 4:42 ` Bhupal Singh
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=512F414E.5090203@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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