From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Gemspecs / Add ruby-ruby-engine.
Date: Tue, 05 Jan 2016 17:53:08 +0100 [thread overview]
Message-ID: <8760z83r4b.fsf@gnu.org> (raw)
In-Reply-To: <idjpoxggk1r.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Tue, 5 Jan 2016 15:47:28 +0100")
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
> But how does this relate to snippets? In other build systems snippets
> cause the source archive to be unpacked, modified, and then repacked.
> If we split unpacking and gemspec extraction we’d have to make sure that
> this also works when snippets are involved, i.e. snippets should see the
> extracted gemspec (as the original one is discarded by the build system
> anyway).
The implementation of snippets is in ‘patch-and-repack’ procedure; it is
completely independent of build systems and their phases.
> Agreed. I’d be happy if someone else could chime in to give an opinion
> on whether to add a new phase or merge gemspec extraction with “unpack”.
I think I don’t understand the issue at hand sufficiently well. Two
things come to mind: “extract” and “unpack” sound synonymous; OTOH,
having a separate phase provides more flexibility, since one can remove
it, replace it, etc.
Ludo’.
prev parent reply other threads:[~2016-01-05 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 7:13 [PATCH] Gemspecs / Add ruby-ruby-engine Ben Woodcroft
2016-01-05 11:36 ` Ricardo Wurmus
2016-01-05 12:09 ` Ben Woodcroft
2016-01-05 14:47 ` Ricardo Wurmus
2016-01-05 16:53 ` Ludovic Courtès [this message]
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=8760z83r4b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.