On 10/21/05, Dave Nebinger <[EMAIL PROTECTED]> wrote: > The devs have finally un-hard-masked MySQL (still soft masked by ~x86 > keyword). But, in their wisdom, they block the 4.1 to 5.0 unless you define > MYSQL_STRAIGHT_UPGRADE=1 before starting the emerge. > > I originally allowed ~x86 because I wanted the 4.1 version of the db, and > everything has been working fine on my end. But now it's time to consider > whether or not to keep the ~x86 keyword and move to the 5.0 branch or remove > it to stay at 4.1. > > Has anyone out there done the 4 to 5 upgrade? What will I need to do > post-install to migrate my databases? > > Also I hestitate to ask if I should do the upgrade; I know folks will say that > it is still soft masked and that's a reason not to do it, but that kind of > response I can do without. A reason outside of the soft-mask that says why I > should not upgrade would be a lot more valuable.
Well, a good reason not to upgrade to 5 is that 5 is, and I quote the MySQL Website, "Development release (use this for previewing and testing new features)" while the 4.1 is still the stable and recommended version. > A google search did not turn up anything gentoo specific about the upgrade, > but I'm still looking for general 4 to 5 upgrading procedures (hmm, maybe > I'll even get to submit a wiki article or something ;-) The Manual for version 5 (from MySQL site) describes the procedures to upgrade better than the ebuild info (IMHO), but it hasn't changed a lot for all versions, backup everything, upgrade, test, if something goes wrong, get it all back from backup, sql files would do better than the data files in this case. Again, I quote the Online Manual at http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html : "Note: Currently, MySQL 5.0 is at Beta status and, as for any other pre-production release, should not be installed on production-level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has done its best to ensure a high level of quality, you should protect your data by making a backup as you would for any software beta release." The rest of the document describes all steps and procedures for a safe upgrade, but keeping in mind that its a TEST version. I'll stick with 4.1 in my server... -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- [email protected] mailing list
