unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr>
Cc: 34644@debbugs.gnu.org, Diego Nicola Barbato <dnbarbato@posteo.de>
Subject: [bug#34644] [PATCH] gnu: Add xsane.
Date: Tue, 26 Feb 2019 15:32:06 +0100	[thread overview]
Message-ID: <20190226153206.738165fa@scratchpost.org> (raw)
In-Reply-To: <87sgwblbnb.fsf@nckx>

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

Hi,

On Mon, 25 Feb 2019 23:57:12 +0100
Tobias Geerinckx-Rice <somebody@not-sent-or-endorsed-by.tobias.gr> wrote:

> Nor I.  It's an interesting situation: snprintf.c seems to have 
> been re-(dual-)licenced under both Artistic and GPL2+OpenSSL 
> exception.
> 
> However, the version shipped with xsane is older (perhaps xsane 
> itself is, even).
> 
> I guess we can just do what Trisquel does and replace it with a 
> newer version.

Sure.

> There's also some talk of a ’system snprintf’ that 
> may or may not do the job without having to provide our own 
> replacement.

If we did that we should mention it upstream--maybe their implementation
has special features that they require that a system implementation
would not have.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-02-26 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-25  1:25 [bug#34644] [PATCH] gnu: Add xsane Tobias Geerinckx-Rice
2019-02-25 21:05 ` Diego Nicola Barbato
2019-02-25 22:57   ` Tobias Geerinckx-Rice
2019-02-26 14:32     ` Danny Milosavljevic [this message]
2019-02-26 14:20 ` Danny Milosavljevic
2019-11-22 21:20   ` bug#34644: " Tobias Geerinckx-Rice via Guix-patches via

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=20190226153206.738165fa@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=34644@debbugs.gnu.org \
    --cc=dnbarbato@posteo.de \
    --cc=somebody@not-sent-or-endorsed-by.tobias.gr \
    /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).