Hello.
>except for shared-compat, for which there is only a 4.1.13 version - is it >acceptable that that RPM be a rev back from the rest? In my opinion, this rpm contains only old libraries which don't change with every new release of MySQL. However,I'm agree - it's a bit confusing. >of 4.1.9. Is there any particular reason I should switch to the RPMs for >glibc 2.3, or not? Can I go directly from the one to the other, during an >RPM upgrade, with no issues? I don't see the reason why you should switch to the glibc 2.3 version. glibc 2.2 is a "rock stable" version. However, in my opinion, you shouldn't have any problems related to glibc. "Shaun T. Erickson" <[EMAIL PROTECTED]> wrote: >I have a CentOS-3 (RHEL 3 equivalent) with MySQL 4.1.9 installed from the >MySQL site. The RPMs I'm using are: > >MySQL-server-4.1.9-0 >MySQL-client-4.1.9-0 >MySQL-devel-4.1.9-0 >MySQL-Max-4.1.9-0 >MySQL-shared-compat-4.1.9-0 > >I see that 4.1.14 is the latest version. When I went to download the latest >RPMs, I got confused though. There are 4.1.14 versions of all of the above, >except for shared-compat, for which there is only a 4.1.13 version - is it >acceptable that that RPM be a rev back from the rest? > >Also, I see that there are glibc 2.3 versions of the above. I have >glibc-2.3.2-95.33 installed. I'm not currently running the glibc 2.3 version >of 4.1.9. Is there any particular reason I should switch to the RPMs for >glibc 2.3, or not? Can I go directly from the one to the other, during an >RPM upgrade, with no issues? > >Anything else I didn't think of? :) -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
