unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Jakob L. Kreuze" <zerodaysfordays@sdf.lonestar.org>
Cc: 36411@debbugs.gnu.org
Subject: [bug#36411] [PATCH] gnu: Add libresprite.
Date: Sat, 29 Jun 2019 17:27:30 +0200	[thread overview]
Message-ID: <87woh4bee5.fsf@nckx> (raw)
In-Reply-To: <8736jthkkd.fsf@sdf.lonestar.org>

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

Jakob,

I didn't check all the bundled packages, but at least freetype2 
and libpng are trivial to unbundle (not patched in any way) and 
probably the most important to, security-wise, so things are 
looking good even if upstream wouldn't cooperate.

Jakob L. Kreuze wrote:
>> Synopsis?
>
> Inherited from 'aseprite'.  Should I alter it to mention that
> it's a fork of Aseprite?

It's certainly not important enough to include in the synopsis, so 
inheriting that is fine.

Now, I'd say it needn't be added to the description either.  We 
generally don't note the often chequered ancestry of our packages, 
nor the fact that they are ‘free’ or ‘open source’, and this is 
just a combination of the two.  But at least description space is 
cheaper if you disagree.  ;-)

Thanks for your work on Guix,

T G-R

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

  parent reply	other threads:[~2019-06-29 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28  0:43 [bug#36411] [PATCH] gnu: Add libresprite Jakob L. Kreuze
2019-06-28  5:28 ` swedebugia
2019-06-28 14:05   ` Jakob L. Kreuze
2019-06-28 15:51     ` swedebugia
2019-06-28 21:23       ` Jakob L. Kreuze
2019-06-29 14:39         ` Christopher Lemmer Webber
2019-06-30  0:45           ` Jakob L. Kreuze
2019-06-29 15:27     ` Tobias Geerinckx-Rice [this message]
2019-06-29 17:10       ` swedebugia
2019-06-30  0:49       ` Jakob L. Kreuze
2021-11-21 23:03 ` bug#36411: " Julien Lepiller

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=87woh4bee5.fsf@nckx \
    --to=me@tobias.gr \
    --cc=36411@debbugs.gnu.org \
    --cc=zerodaysfordays@sdf.lonestar.org \
    /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).