<div dir="ltr">Thanks Ken! That was really helpful. I guess I have to wait until Kushal and my mentor give me a go. I will be packaging a few gems anyway. So, I will be reading all the doc and wiki available, so far I have been pointed to these:<div><br></div><div>1. <a href="http://www.isitfedoraruby.com/">isitfedoraruby</a></div><div>2. <a href="http://fedoraproject.org/wiki/Infrastructure/AppBestPractices">Infrastructure/AppBestPractices</a></div><div>3. <a href="https://fedoraproject.org/wiki/Packaging:Guidelines">Packaging:Guidelines</a></div><div>4. <a href="https://fedoraproject.org/wiki/Packaging:Ruby">Packaging:Ruby</a><div><br></div><div>Let me know if I am missing out on any other important resource.</div><div><br></div><div>Aditya</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 29, 2015 at 2:08 AM, Ken Dreyer <span dir="ltr"><<a href="mailto:ktdreyer@ktdreyer.com" target="_blank">ktdreyer@ktdreyer.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, May 28, 2015 at 2:13 PM, Aditya Prakash<br>
<<a href="mailto:aditya.prakash132@gmail.com">aditya.prakash132@gmail.com</a>> wrote:<br>
> How<br>
> important it is that gems I am using have rpm available? A good amount of<br>
> development time will be wasted in packaging if this is a requirement.<br>
<br>
</span>I've had to take a break from Rails packaging for a while since I<br>
switched jobs, but I still maintain several rubygems with the hope<br>
that I'll be able to do more Ruby/Rails packaging eventually. But I've<br>
been working at it for years, and you're right, packaging each gem<br>
individually is a mountain of work.<br>
<br>
Quick wins are important in a project as big as what you're<br>
discussing, and when packaging gem-by-gem, it's easy to get bogged<br>
down. If I were you, I'd break GlitterGallery down into more<br>
manageable steps:<br>
<br>
Phase 1) Create an RPM that more-or-less follows all the packaging<br>
guidelines, but bundles all its dependencies. You can build/ship this<br>
RPM via Copr.<br>
<br>
Phase 2) Switch your application from using Bundler to using<br>
<a href="https://rubygems.org/gems/bundler_ext" target="_blank">https://rubygems.org/gems/bundler_ext</a><br>
<br>
Phase 3) Start dropping your bundled gems one by one and use the<br>
system gems instead.<br>
<br>
In hindsight I wish that I had taken this approach with Gitorious or<br>
Gitlab, instead of only starting at the base of the dependency tree<br>
and working my way upwards. It's probably good to work from both<br>
directions at once. But starting at the top, with the app itself, will<br>
give you the satisfaction and internal motivation of having something<br>
that works today, even if it's not up to Fedora's standards.<br>
<span class=""><br>
> Also, how important it is that rpm package are available for ruby gems in<br>
> general? In name of being a ruby developer and part of fedora community I<br>
> would like to package a few important ones.<br>
<br>
</span>From my own experience, I've found that packaging gems in Fedora is a<br>
good excuse for learning Ruby, Bundler, Rubygems, Minitest, Rspec, and<br>
other parts of the Ruby ecosystem that touch on packaging.<br>
<br>
- Ken<br>
_______________________________________________<br>
ruby-sig mailing list<br>
<a href="mailto:ruby-sig@lists.fedoraproject.org">ruby-sig@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/ruby-sig" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/ruby-sig</a></blockquote></div><br></div>