The best way to stay current with MySQL new versions is not to install its SuSE implementation in a first place. Assuming that you already have your SuSE Mysql installation. Download fresh MySQL source and put these configuration option into a file with exec permissions. Modify it as needed, drop it into unpacked mysql-4.x.x directory and execute. --------------------------------------------------------------------- #!/usr/bin/bash # MySQL Server with SSL support for x86 systems CC=gcc \ CFLAGS="-O3" \ CXX=gcc \ CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" \ ./configure \ --prefix=/usr/local/mysql \ --enable-assembler \ --enable-fast-install=yes \ --enable-large-files \ --enable-local-infile \ --with-charset=latin1 \ --with-vio \ --with-openssl \ --with-raid \ --with-mysqld-user=mysql \ --without-isam \ --without-docs \ --without-bench \ --without-comment \ --without-debug make scripts/make_binary_distribution.sh ---------------------------------------------------------------------- then copy that mysql-x.x.x.tar.gz file into /usr/local unpack it and set directory permissions to mysql user/group Check your config files left from SuSE modify them as needed. Then start new mysql server and there you go. "If you like to ride a sled, you have to like pulling it first" On Thu, Dec 16, 2004 at 11:25:36AM -0500, Don Parris wrote:
I want to upgrade from the stock MySQL 4.0.24 that came with SUSE 9.2 to 4.1.7. The last time I upgraded, I followed the MySQL instructions (copy current files/folders to *.old), which worked to a point. I got the server working, etc., but had to start it manually, as I didn't understand the instructions for starting it at boot time.
I want to use Yast this time 'round, but am not sure which option to use. Should I use YOU, instead of Install/Remove Software? Or should I scrap it, and just follow the MySQL instructions? Or maybe I can install the new server to a different location?
I have downloaded the RPM's, and they reside on an NFS share. I have added that share as an installation source via Yast. Yast does see the new source - all the RPMs show up in the selection frame. I have also disabled the CD as a source for the moment - not sure if I should do this or not.
At any rate, Yast doesn't seem to want to let me upgrade at all. If I use the Install/Remove option in Yast to remove the current installation first that breaks dependencies that I am not sure will be restored in adding the new MySQL version. 'Package --> All in this List' offers 'Update if new package exists" option, but nothing happened.
I need to resolve this so I can test my SQL scripts for CHADDB (developed on MySQL 3.23.xx) on the newer server.
Thanks, Don
-- DC Parris GNU Evangelist http://matheteuo.org/ http://chaddb.sourceforge.net/ "Free software is like God's love - you can share it with anyone anytime anywhere!"
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com