From: Ricardo Wurmus <rekado@elephly.net>
To: Andreas Enge <andreas@enge.fr>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Add MAFFT.
Date: Sun, 26 Jul 2015 12:16:06 +0200 [thread overview]
Message-ID: <87zj2jw7fd.fsf@elephly.net> (raw)
In-Reply-To: <20150726094338.GA24898@debian>
Andreas Enge <andreas@enge.fr> writes:
> On Sun, Jul 26, 2015 at 01:10:14PM +1000, Ben Woodcroft wrote:
>> I'm actually a bit confused as to the difference between a snippet vs. a
>> patch stage as above - when is each appropriate? Snippets are only for
>> removing non-free software?
>
> I would use a snippet for something internal to Guix, or specific to the
> way we handle things, while a patch is intended to be passed upstream (or
> sometimes taken from upstream already) to correct a bug in the software.
It should be noted that changes performed by snippets directly affect
the resulting tarball produced by ‘guix build -S’. Whenever you want
the sources for a package to be permanently modified for the users, a
snippet would be the right way to achieve that.
next prev parent reply other threads:[~2015-07-26 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 12:43 [PATCH] Add MAFFT Ben Woodcroft
2015-07-25 19:26 ` Ricardo Wurmus
2015-07-26 3:10 ` Ben Woodcroft
2015-07-26 9:43 ` Andreas Enge
2015-07-26 10:16 ` Ricardo Wurmus [this message]
2015-07-26 10:29 ` Andreas Enge
2015-07-31 22:42 ` Ben Woodcroft
2015-08-25 20:58 ` Ludovic Courtès
2015-09-07 8:55 ` Andreas Enge
2015-09-07 9:07 ` Ricardo Wurmus
2015-09-12 12:20 ` Ben Woodcroft
2015-09-16 20:19 ` Ludovic Courtès
2015-09-16 21:09 ` Ricardo Wurmus
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=87zj2jw7fd.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=andreas@enge.fr \
--cc=guix-devel@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).