Ciro Iriarte wrote: > 2007/8/9, Michal Marek <[EMAIL PROTECTED]>: >> Ciro Iriarte wrote: >>> Probably i'll copy the datafiles (as soon as i get the needed space) >>> to a vmware installation and try to update mysql or probably reinstall >>> it (rpm -e mysql/rpm -i mysql-5.blah). >> If you have the possibility to test your app in a testing environment, >> then this is definitely the recommended way. rpm -Uvh should work as > > That probably won't do it, the package are not the same. We currently have: > > mysql-4.1.10a-3.4 <---- taken from suse 9.3 > mysql-client-4.1.10a-3 <---- taken from suse 9.3 > mysql-shared-4.0.18-32.1 <--- stock, needed by php and other > packages. It'll be a mess to try to compile php with the new libs i > guess > mysql-devel-4.0.18-32.20 <--- stock too > > MySQL5: > > libedit-devel-2.10.snap20070302-11.1.x86_64.rpm > libedit0-2.10.snap20070302-11.1.x86_64.rpm <--- huh? > > libmysqlclient-devel-5.0.45-2.1.x86_64.rpm > libmysqlclient15-5.0.45-2.1.x86_64.rpm <--- confused > libmysqlclient_r15-5.0.45-2.1.x86_64.rpm <--- confused > > mysql-5.0.45-2.1.x86_64.rpm <--- goes in > mysql-Max-5.0.45-2.1.x86_64.rpm <-- not interested in > mysql-bench-5.0.45-2.1.x86_64.rpm <-- not interested in > mysql-client-5.0.45-2.1.x86_64.rpm <--- goes in > mysql-debug-5.0.45-2.1.x86_64.rpm <-- not interested in > mysql-test-5.0.45-2.1.x86_64.rpm <-- i don't think we need it > mysql-tools-5.0.45-2.1.x86_64.rpm <-- not sure > pgpool-3.1.1-4.3.x86_64.rpm <-- sounds out of place
And what's the problem? 'rpm -Uvh mysql-5.0.*.rpm mysql-client-5.0.*.rpm libmysqlclient15-5.0.*.rpm' will give you a working mysql5 setup. And it'll keep the 4.x libs for apps linked against it (php). Michal -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
