all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Building AbiWord without libwmf and removing libwmf from Guix
Date: Sun, 28 May 2017 22:57:49 +0200	[thread overview]
Message-ID: <87tw44n1gy.fsf@gnu.org> (raw)
In-Reply-To: <20170528184450.GD15883@jasmine> (Leo Famulari's message of "Sun, 28 May 2017 14:44:50 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Sun, May 28, 2017 at 03:06:35PM +0200, Hartmut Goebel wrote:
>> Am 27.05.2017 um 23:13 schrieb Ricardo Wurmus:
>> > I think it would be better to remove libwmf.
>> +1
>
> Something to consider is that many of our packages can be described as
> unmaintained and full of bugs. And even the packages that are maintained
> may be full of bugs, too.

True.  The best solution would be for our OS to run every program in an
isolated environment, like Plash or like Qubes.  That would allow us to
live with these bugs somewhat more peacefully.  We should work in that
direction, maybe using containers, which are imperfect but readily
available and an improvement over the status quo.

In the meantime, we probably need to take care of our packages though,
and provide security fixes or remove them.

Given what you and Ricardo wrote about libwmf, it seems to me that
removing it would be wise.

Thoughts?

Ludo’.

  reply	other threads:[~2017-05-28 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 17:06 Building AbiWord without libwmf and removing libwmf from Guix Leo Famulari
2017-05-27 19:41 ` Mark H Weaver
2017-05-27 21:13   ` Ricardo Wurmus
2017-05-28 13:06     ` Hartmut Goebel
2017-05-28 18:44       ` Leo Famulari
2017-05-28 20:57         ` Ludovic Courtès [this message]
2017-06-23 22:30           ` Leo Famulari
2017-06-24  8:12           ` ng0
2017-06-24  8:02     ` ng0
2017-06-24 16:21       ` Leo Famulari
2017-06-24 22:52         ` Mark H Weaver
2017-06-25  3:37           ` Leo Famulari

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=87tw44n1gy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.