<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dne 3.1.2012 18:40, Michael Stahnke napsal(a):
<blockquote
cite="mid:CA+_jt2ZGrV+2Lw2qFGx8+3pTstvWu-zCPG3q9i5_E5Ci36pR2A@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Tue, Jan 3, 2012 at 7:21 AM, Vít
Ondruch <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:vondruch@redhat.com">vondruch@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everybody,<br>
<br>
I am wondering if we should mention Bundler in Ruby's
packaging guidelines and what should be recommendations? Or
should we leave it in gray area of guidelines?<br>
<br>
Thinking about it again and again, I believe that we should
discourage usage of Bundler in Fedora. What is your opinion?<br>
</blockquote>
<div><br>
</div>
<div>I really dislike bundler. However, from the Ruby ecosystem
point of view, it's there and it's not going anywhere. It
featured on every rubygem page. It certainly conflicts with
the bundled library viewpoint Fedora has, but without it, many
many applications built upon Ruby won't make it into Fedora.
This is especially true since rpm by design cannot have
multiple versions of the same package installed; whereas gem
can. </div>
<div><br>
</div>
<div>So, I hate bundler, and I don't think we should allow it.
We should however, be aware of how that will hinder Fedora as
a ruby development and deployment platform.</div>
</div>
</blockquote>
<br>
<br>
My intention was not in a sense of "retire Bundler", definitely not.
However, I would like to clarify what is our position and
suggestions for packagers.<br>
<br>
For example, something along the lines:<br>
<br>
1) If test suite is designed to run with Bundler, please run "$ sed
-i -e 's|require "bundler"||' spec/spec_helper.rb" and "$ sed -i -e
's|Bundler.setup||' spec/spec_helper.rb" to remove the dependency
and run the test suite without it.<br>
<br>
2) If Rails application uses Bundler, remove the dependency by
deleting the Gemfile and Gemfile.lock and the dependency
initialization move into some Rails app initializer (not sure if
this approach is feasible). Gemfile and Gemfile.lock *must not* be
included in package.<br>
<br>
<br>
I can imagine other variants of the second point like:<br>
<br>
2a) Provide specific Gemfile.lock for each Fedora version. However
this is fragile, since update of one gem may break the application.<br>
<br>
2b) Delete Gemfile.lock from package and run the application for the
first time with root privileges.<br>
<br>
2c) After first execution, Gemfile.lock is created in some world
writable directory, probably somewhere in /var. However this would
need patched version of Bundler.<br>
<br>
<br>
As you can see, there is a lot of options, neither one ideal.
Question is which one we should pick?<br>
<br>
<br>
From developer's point of view, I believe that Bundler has its
advantages and I support its usage (may be not for 100% but I see
some use-cases). The adjustments necessary for Fedora should be done
by packager. If they are done sensitively and in collaboration with
upstream, then it is ideal.<br>
<br>
<br>
Does anybody knows what is Debian's view of Bundler for example?<br>
<br>
<br>
Vit<br>
</body>
</html>