all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 33347@debbugs.gnu.org
Subject: [bug#33347] [PATCH 4/4] gnu: teeworlds: Update to 0.7.0 [fixes CVE-2018-18541].
Date: Wed, 14 Nov 2018 12:39:31 -0500	[thread overview]
Message-ID: <20181114173931.GB2408@jasmine.lan> (raw)
In-Reply-To: <8736s33hnq.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]

On Wed, Nov 14, 2018 at 09:36:25PM +0800, Alex Vong wrote:
> Well, I though we have a policy to remove bundle dependencies in order
> to avoid building the same library many times. Do we make exceptions for
> shared libraries w/o a build system? (an exception I can think of is
> gnulib)

In general, yes, our policy is to unbundle things when practical.

But there are some commonly used software implementations of basic
functions (like base64, sha1 (most hash functions actually), et cetera)
that are specifically designed to be copied and pasted into the
application that will be using them.

You can usually tell this is the case because the thing will not have
any build system at all, like you suggest. Also because you find the
same copy-pasted code in almost every program you look at, like with
base64 and the hash functions.

> Besides, the FIXME comment seems to suggest future readers to help
> remove the bundled pnglite. Debian also removes the bundled pnglite in
> teeworlds[0].

Well, at a certain point it becomes a matter of taste, and the choice
should be made by the person doing the work — you! Either way is fine
for Guix :) The important thing is to get this Teeworlds fix pushed
without too much delay.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-14 17:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-11 19:03 [bug#33347] [PATCH 0/4] gnu: teeworlds: Update to 0.7.0 [fixes CVE-2018-18541] Alex Vong
2018-11-11 19:06 ` [bug#33347] [PATCH 1/4] gnu: Add pnglite Alex Vong
2018-11-11 19:07 ` [bug#33347] [PATCH 2/4] gnu: Add json-parser Alex Vong
2018-11-13 16:49   ` Leo Famulari
2018-11-14 13:19     ` Alex Vong
2018-11-11 19:09 ` [bug#33347] [PATCH 3/4] " Alex Vong
2018-11-13 16:47   ` Leo Famulari
2018-11-14 13:14     ` Alex Vong
2018-11-11 19:09 ` [bug#33347] [PATCH 4/4] gnu: teeworlds: Update to 0.7.0 [fixes CVE-2018-18541] Alex Vong
2018-11-13 16:53   ` Leo Famulari
2018-11-14 13:36     ` Alex Vong
2018-11-14 17:39       ` Leo Famulari [this message]
2018-11-14 21:14         ` Alex Vong
2018-11-21 14:41           ` Alex Vong
2018-11-21 16:14             ` Leo Famulari
2018-11-21 16:14               ` Leo Famulari
2018-11-21 19:51               ` Alex Vong
2018-11-11 19:13 ` [bug#33347] [PATCH 0/4] " Alex Vong
2018-11-13 16:54 ` 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=20181114173931.GB2408@jasmine.lan \
    --to=leo@famulari.name \
    --cc=33347@debbugs.gnu.org \
    --cc=alexvong1995@gmail.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.
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.