From: swedebugia <swedebugia@riseup.net>
To: 36411@debbugs.gnu.org
Subject: [bug#36411] [PATCH] gnu: Add libresprite.
Date: Sat, 29 Jun 2019 19:10:00 +0200 [thread overview]
Message-ID: <909e98f0-d945-3e23-0600-0ce09930e960@riseup.net> (raw)
In-Reply-To: <87woh4bee5.fsf@nckx>
On 2019-06-29 17:27, Tobias Geerinckx-Rice wrote:
> 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. ;-)
What about noting it in the top of the recipe as a comment?
";; This is a fork of xx"
I find that helpful but it might be unnecessary too?
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-06-29 17:11 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
2019-06-29 17:10 ` swedebugia [this message]
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=909e98f0-d945-3e23-0600-0ce09930e960@riseup.net \
--to=swedebugia@riseup.net \
--cc=36411@debbugs.gnu.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).