<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This sounds like a good feature to add to the site. It could simply
be accomplished by listing the gems available for every Fedora
version + rawhide along w/ their versions and other metadata.<br>
<br>
This metadata can include a list of patches applied to the gem (as
well as direct access to their contents if we wanted). We can
extract this information directly from the (s)rpm itself.<br>
<br>
Going forward, if we start standardizing on patch names, it might
make it easier to automate parsing patch information from the srpm.
I always try naming patches %{gemname}-%{version}-%{some general
subject/description}<br>
<br>
We will look at producing some mockups for this feature and
implementing them as part of the GSoC (keep those suggestions
coming!)<br>
<br>
BTW as a related side note, I'm looking for a co-mentor for this
project. The person will not have to do anything except for have
their name appear on the list as a formality to the GSoC process. If
you're interested please ping me on or off list (asap please as the
final project evaluation deadline is in a few days)<br>
<br>
Appreciate it,<br>
-Mo<br>
<br>
<br>
<br>
On 04/15/2012 05:46 PM, Wan Zuhao wrote:
<blockquote cite="mid:1C41B9339CA14BF09A6DB9F953EE09ED@gmail.com"
type="cite">
<div>I do agree that it's very likely to miss out information such
as patches and bug fixes applied if we rely on gem versions
solely. </div>
<div><br>
</div>
<div>Maybe we can compare the timestamp of the built rpm to that
of the gem commits? Then we can roughly tell by the time the rpm
was built, which patches have already been applied. Apparently
this method can't be 100% accurate. I'm trying to figure out
some other more reliable way, but I'm still kinda new to the
Fedora dev community, so it will probably take some time for me
to get a better grip on these. I'll have to dig deeper to see
exactly what information is available.</div>
<div><br>
</div>
<div>By the way, could you please give some examples of such
gem/rpm?</div>
<div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Zuhao</div>
</div>
<p style="color: #A0A0A8;">On Sunday, April 15, 2012 at 11:31 PM,
Wan Zuhao wrote:</p>
<blockquote type="cite"
style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div>I see your point. </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div><br>
</div>
</div>
<p style="color: #A0A0A8;">On Sunday, April 15, 2012 at
9:37 AM, Jeroen van Meeuwen (Kolab Systems) wrote:</p>
<blockquote type="cite">
<div> <span>
<div>
<div>
<div>On 2012-04-14 21:08, Wan Zuhao wrote:</div>
<blockquote type="cite">
<div>
<div>Hi Jeroen,</div>
<div><br>
</div>
<div>What you've suggested is definitely a
good idea. I do agree it's </div>
<div>important</div>
<div>to reflect which *version*, in addtion
to the name, link, etc. of a</div>
<div>particular gem that was converted into
rpm, as sometimes the latest </div>
<div>patches</div>
<div>and bug fixes are not included in the
rpm.</div>
</div>
</blockquote>
<div><br>
</div>
<div>The point is also, sometimes bug fixes
(especially security issues) </div>
<div>*are* in fact included in the RPM, but the
gem/rpm package version </div>
<div>number would not reflect that.</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div>Jeroen van Meeuwen</div>
<div><br>
</div>
<div>-- </div>
<div>Systems Architect, Kolab Systems AG</div>
<div><br>
</div>
<div>e: vanmeeuwen at <a moz-do-not-send="true"
href="http://kolabsys.com">kolabsys.com</a></div>
<div>m: +44 74 2516 3817</div>
<div>w: <a moz-do-not-send="true"
href="http://www.kolabsys.com">http://www.kolabsys.com</a></div>
<div><br>
</div>
<div>pgp: 9342 BF08</div>
<div>_______________________________________________</div>
<div>ruby-sig mailing list</div>
<div><a moz-do-not-send="true"
href="mailto:ruby-sig@lists.fedoraproject.org">ruby-sig@lists.fedoraproject.org</a></div>
<div><a moz-do-not-send="true"
href="https://admin.fedoraproject.org/mailman/listinfo/ruby-sig">https://admin.fedoraproject.org/mailman/listinfo/ruby-sig</a></div>
</div>
</div>
</span> </div>
</blockquote>
<div> <br>
</div>
</div>
</div>
</span> </blockquote>
<div> <br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ruby-sig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ruby-sig@lists.fedoraproject.org">ruby-sig@lists.fedoraproject.org</a>
<a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/mailman/listinfo/ruby-sig">https://admin.fedoraproject.org/mailman/listinfo/ruby-sig</a></pre>
</blockquote>
<br>
</body>
</html>