<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rubygem on Saleem Ansari</title>
    <link>/tags/rubygem/</link>
    <description>Recent content in Rubygem on Saleem Ansari</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>(c) 2024 Saleem Ansari</copyright>
    <lastBuildDate>Sun, 04 Mar 2012 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/rubygem/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Problems with Ruby GEM to RPM</title>
      <link>/2012/03/04/problems-with-ruby-gem-to-rpm/</link>
      <pubDate>Sun, 04 Mar 2012 00:00:00 +0000</pubDate>
      <guid>/2012/03/04/problems-with-ruby-gem-to-rpm/</guid>
      <description>I can&amp;rsquo;t emphasize more the importance of packaging RPMs ( or any other packaging system ), as I already did it in an earlier post.&#xA;Same arguments apply to Ruby Gems as well. That is to say, Ruby Gems already have a gem command to install and update packages. However it is still not a complete packaging system in itself.&#xA;Consider the situation where you need to install a gem called A which dependes on B and C.</description>
    </item>
  </channel>
</rss>
