<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dne 10.11.2015 v 16:09 Troy Dawson
napsal(a):<br>
</div>
<blockquote
cite="mid:CAKndyUTX18GqrKNo_j4fUxpdQrRXow2sRdfXRnsDyiH=__LhBg@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Nov 10, 2015 at 8:52 AM, Vít
Ondruch <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:vondruch@redhat.com" target="_blank">vondruch@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hi guys,<br>
<br>
For a long time, I thought that it would be interesting to
have .gem<br>
expansion support in %setup macro. This would simply our
.spec files a<br>
bit. Finally, I gave a go to this idea and proposed this
to RPM upstream<br>
[1]. Please let me know (preferably via the PR) if you can
foresee any<br>
issues with this approach.<br>
<br>
Thanks.<br>
<br>
<br>
Vít<br>
<br>
<br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/rpm-software-management/rpm/pull/27"
rel="noreferrer" target="_blank">https://github.com/rpm-software-management/rpm/pull/27</a><br>
_______________________________________________<br>
ruby-sig mailing list<br>
<a moz-do-not-send="true"
href="mailto:ruby-sig@lists.fedoraproject.org">ruby-sig@lists.fedoraproject.org</a><br>
<a moz-do-not-send="true"
href="https://admin.fedoraproject.org/mailman/listinfo/ruby-sig"
rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/ruby-sig</a></blockquote>
</div>
<br>
<div>
<div>
<div>
<div>Hi Vit,<br>
</div>
I think this is a great idea. Since the instructions
for prep of rubygems have settled down for a couple
years I think now is the time to do it.<br>
<br>
</div>
I do have one question.<br>
</div>
If I am reading the code right you have the equivalent of<br>
</div>
{gem unpack} SOURCE0 && gem spec SOURCE0 --ruby >
{gem_name}.gemspec
<div><br>
</div>
<div>Why aren't you using the -l in the gem spec portion?<br>
</div>
<div>Shouldn't it be<br>
<br>
{gem unpack} SOURCE0 && gem spec SOURCE0 -l --ruby
> {gem_name}.gemspec<br>
</div>
<div><br>
</div>
<div>Troy<br>
<br>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<br>
Thank you, that is a good point. I omitted it just by accident. On
the other hand, what is the practical difference? Not sure. I should
probably dive a bit into RubyGems code.<br>
<br>
<br>
Vít<br>
</body>
</html>