On Tue, 2012-08-21 at 14:05 -0500, Jordon Bedwell wrote: > On Tue, Aug 21, 2012 at 1:10 PM, shawn <[email protected]> wrote: > > On Tue, 2012-08-21 at 13:07 -0500, Jordon Bedwell wrote: > >> On Tue, Aug 21, 2012 at 1:02 PM, shawn <[email protected]> wrote: > >> > you should read the bug. rubygems->ruby1.8 > >> > rubygems1.9.1->ruby1.9.1 (now provided: by ruby1.9.1(really 1.9.3)) > >> > >> Absolutely right, I missed that, looks like the rubygems depend needs > >> to be put directly onto ruby1.8 instead of on packages like hoe. > > > > no that is wrong, as ruby1.8 doesn't embed rubygems like ruby1.9.3 does. > > We should not force people to use rubygems just becuase they use > > ruby1.8. > > While I agree with assessment that it should not be forced (which is > what recommend dependencies are for) I do not agree with the > assumption that it should not be attached to ruby1.8. Your point on it > being embedded is moot and out-of-context anyways considering it > wouldn't be there as an external dependency if it was embedded and > technically it's not embedded it's included.
Well 1.8 is going to be dropped after 1.8, so this argument is close to obsolete. -- -Shawn Landden -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/1345578118.29580.156.camel@shawn-ssd
