On 12/22/2011 09:09 AM, Vít Ondruch wrote:
>
> - In the Rubygems section:
>
> "For every dependency on a Gem named|gemdep|, the package must contain
a|Requires| on|rubygem(%{gemdep})| with the same version constraints as the Gem"
>
> Can this be a "should" or can we append a "where possible" onto
the end of this. I've run into situations in the past where the constraints on the
upstream gem are too restrictive, and infact the gem will work with a more lax gem set
which we ship in Fedora
You are right. We should not be as strict. Actually, I believe that we
should not use version unless necessary. We will try to polish this
formulation according to your suggestion.
Actually, we need to be very careful
here. We've been bitten in the past
by creating RPMs with deps that don't strictly follow the gem deps,
since you then have a gem installed that, strictly speaking, doesn't
meet its gem dep requirements. If you end up using bundler for
something, it's going to complain. We had a big problem with this when
we had an RPM for which the underlying gem required rspec (2.0+), but we
required the rspec sub-packages instead.
Scott