On 08/05/2011 08:13 AM, Vít Ondruch wrote:
Option 3 is my favorite.
Since bundler serves only to manage package dependencies with gem,
whereas we are trying to manage them w/ rpm, I agree it makes sense to
decouple these bits where feasible.
That being said, I'm wondering if this is all this strictly necessary.
The bundler situation for Rails and other packages already in the yum
repos is already taken care of.
And as far as the upstream projects we manage, such as Katello and
Aeolus, we have to select a Ruby stack to work against anyways. That
ruby stack can be represented in the Gemfile.lock in our git repos, and
whenever it is time to push a release to Fedora we can patch the
Gemfile.lock in the rpm spec.
An issue w/ removing bundler from the project is that the Ruby community
has come to expect this w/ Rails applications. While we have to deviate
somewhat to conform to Fedora guidelines, staying as close as we can to
upstream Ruby practices is the best way to making Fedora the most
relevant platform for Ruby development and to get our own projects
accepted / used by the wider Ruby community.
Thoughts?
-Mo