Ricardo Wurmus 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. sn
Ben Woodcroft writes:
> On 05/01/16 21:36, Ricardo Wurmus wrote:
>> Ben Woodcroft writes:
> [..]
>>> While I managed to install 1.0.1, I wasn't sure how best to remove the
>>> bundled 1.0.0 .gem file. The issue is that when the source is a .gem
>>> file (ie most of the time), the gemspec is tak
On 05/01/16 21:36, Ricardo Wurmus wrote:
Ben Woodcroft writes:
[..]
While I managed to install 1.0.1, I wasn't sure how best to remove the
bundled 1.0.0 .gem file. The issue is that when the source is a .gem
file (ie most of the time), the gemspec is taken from the downloaded
.gem file direc
Ben Woodcroft writes:
> I've attached a patch for a simple rubygem. This one was slightly nasty
> because the gem for version 1.0.1 includes the .gem file for version
> 1.0.0, which means that 1.0.0 gets silently installed instead of the
> built and tested 1.0.1 .gem file - it is unlucky that
Hi Guix,
I've attached a patch for a simple rubygem. This one was slightly nasty
because the gem for version 1.0.1 includes the .gem file for version
1.0.0, which means that 1.0.0 gets silently installed instead of the
built and tested 1.0.1 .gem file - it is unlucky that
"pkg/ruby-engine-1.0