There are specific cases where running the latest branch of software is not ideal. For example, GeoDjango on MySQL 5.5 seems to be broken, so in order to use it I require MySQL 5.1 (for now). It seems there is no way to be on the latest '5.1'... but only revert to the last 5.1 I had installed. Would be ideal to have major version branches. For example 'mysql.rb' may be the latest stable version, and always the latests stable... but also maintain the latest stable 5.1 release in mysql51.rb. I think this would be warranted for plenty of other formulas, but this is the only one that has bitten me.
My resolution was to look through the git history, find the last '5.1' version of the formula.. then update it for the latest mysql 5.1.58. ... which was a pain.
Hello,
There are specific cases where running the latest branch of software is not ideal. For example, GeoDjango on MySQL 5.5 seems to be broken, so in order to use it I require MySQL 5.1 (for now). It seems there is no way to be on the latest '5.1'... but only revert to the last 5.1 I had installed. Would be ideal to have major version branches. For example 'mysql.rb' may be the latest stable version, and always the latests stable... but also maintain the latest stable 5.1 release in mysql51.rb. I think this would be warranted for plenty of other formulas, but this is the only one that has bitten me.
My resolution was to look through the git history, find the last '5.1' version of the formula.. then update it for the latest mysql 5.1.58. ... which was a pain.