On Nov 12, 2007, at 5:35 PM, Michael Koziarski wrote:
> > The changes like render_action disappearing only happened in trunk, so > you're obviously running the 'fake' 1.2.x releases which are now > labeled more clearly. bingo. thanks all - problem solved. i'm still pretty unclear about the versioning policy though (arbitrary svn tags which are not embeded in gems aside). i was after something a bit more concrete such as http://rubygems.org/read/chapter/7#page26 or, quoting from http://www.gnu.org/software/libtool/manual.html#Libtool-versioning " So, libtool library versions are described by three integers: current The most recent interface number that this library implements. revision The implementation number of the current interface. age The difference between the newest and oldest interfaces that this library implements. In other words, the library implements all the interface numbers in the range from number current - age to current. If two libraries have identical current and age numbers, then the dynamic linker chooses the library with the greater revision number. " and the comments on a 1.99 version that is not backward compatible with 1.2.x make me wonder: what is this.that.andthat supposed to mean in a rails version tag *exactly* ?? kind regards. a @ http://codeforpeople.com/ -- share your knowledge. it's a way to achieve immortality. h.h. the 14th dalai lama --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
