Mailinglist Archive: opensuse-ruby (11 mails)

< Previous Next >
[opensuse-ruby] Packaging rails applications for openSUSE
  • From: Nanuk Krinner <nkrinner@xxxxxxx>
  • Date: Thu, 02 Aug 2012 14:30:18 +0200
  • Message-id: <>

Currently I try to package a Rails application for openSUSE. I ran into a problem and I wonder how to deal with it. Some Rails applications have their gems with them, which we don't want. We want the gems to be in their own package each.

Now comes my problem: My Rails app needs a certain gem, say haml-3.1.2.

In d:l:r:e we have haml-3.1.6. Now I could use the newer version from d:l:r:e and differ from upstream, and I would have to do this for almost every single gem the application needs. This would also require a lot of testing if the application doesn't run properly which is not so unlikely when it uses gems it was not designed for.

Or I could package haml-3.1.2 and submit it to d:l:r:e. But lists 125 different versions of haml. As a worst case we might end up with 125 different haml packages in d:l:r:e.

Or I could create a package that has all the needed gems in its vendor directory. Which is against our packaging policy AFAIK.

So, what should I do? Is there a way to make it easier to package Rails applications for openSUSE? The alternative would be to tell the users to get their Rails applications somewhere else. As I understand it this is the consequence of the current policy. Or am I totally wrong?

What about the idea of having a separate repository where we allow Rails applications with packaged gems?

To unsubscribe, e-mail: opensuse-ruby+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-ruby+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation