From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Icecat crash
Date: Fri, 24 Feb 2017 13:24:01 -0500 [thread overview]
Message-ID: <20170224182401.GA11732@jasmine> (raw)
In-Reply-To: <20170222093801.GA29885@jocasta.intra>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
On Wed, Feb 22, 2017 at 10:38:02AM +0100, John Darrington wrote:
> On Tue, Feb 21, 2017 at 05:44:43PM -0500, Leo Famulari wrote:
> On Wed, Feb 15, 2017 at 11:12:45PM +0100, Julien Lepiller wrote:
> > Hey, I'm also experiencing crashes with icecat since a few months. It
> > just seems to happen randomly. I've found a note about that on the LFS
> > website on the firefox page that says that using system cairo is
> > causing a crash when it tries to do background rendering. So I've
> > changed our icecat recipe to use the bundled version of cairo, and I
> > don't get any crash anymore. Would something like this patch be
> > acceptable?
>
> For serious upstream vendors like Mozilla, one of the reasons they
> bundle things is that they are hitting bugs in the 3rd party library
> that are not fixed upstream.
>
> On the other hand, distros like to unbundle because the upstream vendor
> tends not to patch security vulnerabilities in their bundled copies
> quickly enough, in our opinion.
>
>
> Surely the advantage of a Functional Package Management System like Guix is
> that we have the best of both worlds.
>
> We can specify a *specific* version of a dependency to use (patched if necessary)
> but are not forced to bundle it.
You're right. Now that we've discussed some of the issues involved here,
we can start working on fixing this bug in our package. Any takers?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-24 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 23:34 Icecat crash Danny Milosavljevic
2016-12-26 1:47 ` Chris Marusich
2016-12-26 2:15 ` Leo Famulari
2017-02-15 22:12 ` Julien Lepiller
2017-02-21 22:44 ` Leo Famulari
2017-02-22 8:41 ` ng0
2017-02-22 9:38 ` John Darrington
2017-02-24 18:24 ` Leo Famulari [this message]
2016-12-31 21:37 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170224182401.GA11732@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).