and RDoc versions, just like the ruby one depends on the latest Ruby)
this way you’ll get automagically upgraded to 2.0 if/when the next
Debian stable ships it.
The point of Stable is that it doesn’t change, so that you’ll never have
to worry about something that works suddenly breaking when you’re doing
security updates or adding software. Thus, one tends to not see new
packages appear in Stable unless absolutely necessary for security
reasons.
Anyway, whether you don’t want to upgrade to the next stable release
when it
appears, or whether you do want to, selecting the dummy, generic-named
packages is better.
On Sat, Dec 24, 2005 at 07:44:41AM +0900, Shot - Piotr S. wrote:
this way you’ll get automagically upgraded to 2.0 if/when the next
Debian stable ships it.
The point of Stable is that it doesn’t change, so that you’ll never have
to worry about something that works suddenly breaking when you’re doing
security updates or adding software. Thus, one tends to not see new
packages appear in Stable unless absolutely necessary for security
reasons.
On Sat, Dec 24, 2005 at 07:44:41AM +0900, Shot - Piotr S. wrote:
Or, better yet, ri and rdoc (dummy packages depending on the latest ri
and RDoc versions, just like the ruby one depends on the latest Ruby)
this way you’ll get automagically upgraded to 2.0 if/when the next
Debian stable ships it.
The point of Stable is that it doesn’t change, so that you’ll never
have to worry about something that works suddenly breaking when you’re
doing security updates or adding software. Thus, one tends to not see
new packages appear in Stable unless absolutely necessary for security
reasons.
That’s why I explicitly mentioned I’m writing about upgrading to the
next stable. I prefer to automagically see there’s a new stable Ruby
version and be able to easily choose whether to upgrade (with the
dependencies changed to ruby2.0) or keep the dummy ruby package at
the current version (thus keeping ruby1.8).
Also, in this particular case, the suggestion was already to install the
dummy ruby package; IMHO it only makes sense to do the same for the ri
and rdoc packages (what would be the benefit of upgrading to Ruby 2.0
but keeping the older ri and RDoc?).
Also, Debian releases stable versions fairly rarely, but Ubuntu releases
every six months (and I generally upgrade accordingly); it’s really nice
not to have to track such changes in all of the non-default packages,
and use the dummy ones to do the work. :o)
On Sat, Dec 24, 2005 at 02:45:28PM +0900, angus wrote:
Or, better yet, ri and rdoc (dummy packages depending on the latest ri
Anyway, whether you don’t want to upgrade to the next stable release when it
appears, or whether you do want to, selecting the dummy, generic-named
packages is better.
Sorry, didn’t mean to get pedantic. Yes, you’re right.