Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-10 Thread Tom Lane
Remi Collet writes: > I have just notice, in the spec > -DWITH_READLINE=ON > Which means, according to INSTALL-SOURCE : > * -DWITH_READLINE=bool >Whether to use the readline library bundled with the >distribution. > Does this use of a bundled library is wanted ? Not

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-10 Thread Remi Collet
I have just notice, in the spec -DWITH_READLINE=ON Which means, according to INSTALL-SOURCE : * -DWITH_READLINE=bool Whether to use the readline library bundled with the distribution. Does this use of a bundled library is wanted ? To use the system library, option sh

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-06 Thread Jon Ciesla
Jon Ciesla wrote: > Tom Lane wrote: > >> Jon Ciesla writes: >> >> >>> So should simply patching to call mysql_thread_end instead should do the >>> trick? >>> >>> >> Right. >> >> regards, tom lane >> >> > I'll give that a whirl, thanks! > J > >

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-06 Thread Jon Ciesla
Tom Lane wrote: > Jon Ciesla writes: > >> So should simply patching to call mysql_thread_end instead should do the >> trick? >> > > Right. > > regards, tom lane > I'll give that a whirl, thanks! J -- in your fear, seek only peace in your fear, seek only love -d

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-05 Thread Tom Lane
Jon Ciesla writes: > So should simply patching to call mysql_thread_end instead should do the > trick? Right. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-05 Thread Jon Ciesla
Tom Lane wrote: > Jon Ciesla writes: > >> Tom Lane wrote: >> >>> I got tired of the amount of visible churn in exported-symbols-you're- >>> not-supposed-to-use. The new release will use a linker --version-script >>> to hide everything except the documented API functions. This might >>> b

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-03 Thread Tom Lane
Orcan Ogetbil writes: > On Wed, Dec 22, 2010 at 5:28 PM, Tom Lane wrote: >> For now I'll include a symlink libmysqlclient_r.so -> libmysqlclient.so, >> so that a simple rebuild with no source-code changes should be >> sufficient.  Eventually we'll probably want to fix the source code to >> not re

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-03 Thread Tom Lane
Jon Ciesla writes: > Tom Lane wrote: >> I got tired of the amount of visible churn in exported-symbols-you're- >> not-supposed-to-use. The new release will use a linker --version-script >> to hide everything except the documented API functions. This might >> break any apps that are relying on no

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-03 Thread Orcan Ogetbil
On Wed, Dec 22, 2010 at 5:28 PM, Tom Lane wrote: > For now I'll include a symlink libmysqlclient_r.so -> libmysqlclient.so, > so that a simple rebuild with no source-code changes should be > sufficient.  Eventually we'll probably want to fix the source code to > not refer to libmysqlclient_r, but t

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2011-01-03 Thread Jon Ciesla
Tom Lane wrote: > Since MySQL AB^W^WSun^WOracle has now declared the mysql 5.5.x release > series to be GA status, I'm planning to push it into rawhide shortly to > replace the 5.1.x series. Theoretically, this will go pretty smoothly. > > I'm aware of a couple of ABI-level issues: > > 1. libmysql

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-28 Thread Michał Piotrowski
W dniu 28 grudnia 2010 16:01 użytkownik Michał Piotrowski napisał: > 2010/12/27 Tom Lane : >> =?ISO-8859-2?Q?Micha=B3_Piotrowski?= writes: >>> 2010/12/22 Tom Lane : 1. libmysqlclient.so, which is linked into all manner of stuff, is supposed to be ABI-compatible with the previous release

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-28 Thread Remi Collet
Le 28/12/2010 16:37, Tom Lane a écrit : > mysql-5.5.8-2 should be in the buildroots as of yesterday. Thanks, I have missed the "compose" mail. php rebuild mysql++ rebuild mysql-connector-c++ rebuild mysql-worbench ready, waiting for mysql-connector-c++ in rawhide. Remi. -- devel mailing list de

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-28 Thread Tom Lane
Remi Collet writes: > Le 22/12/2010 23:28, Tom Lane a écrit : >> mysql++ > I've just committed some minor changes to this one (not related to the > MySQL 5.5 update, but on my TODO for a while) > Just need to launch the build (I could do it as soon as -2 will hit rawhide) mysql-5.5.8-2 should

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-28 Thread Remi Collet
Le 22/12/2010 23:28, Tom Lane a écrit : > mysql++ I've just committed some minor changes to this one (not related to the MySQL 5.5 update, but on my TODO for a while) Just need to launch the build (I could do it as soon as -2 will hit rawhide) PHP also build and works fine with -2. Remi. -- de

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-28 Thread Michał Piotrowski
2010/12/27 Tom Lane : > =?ISO-8859-2?Q?Micha=B3_Piotrowski?= writes: >> 2010/12/22 Tom Lane : >>> 1. libmysqlclient.so, which is linked into all manner of stuff, is >>> supposed to be ABI-compatible with the previous releases.  However, >>> I got tired of the amount of visible churn in exported-sy

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-27 Thread Tom Lane
=?ISO-8859-2?Q?Micha=B3_Piotrowski?= writes: > 2010/12/22 Tom Lane : >> 1. libmysqlclient.so, which is linked into all manner of stuff, is >> supposed to be ABI-compatible with the previous releases.  However, >> I got tired of the amount of visible churn in exported-symbols-you're- >> not-suppose

Re: [HEADS-UP] MySQL 5.5 coming soon to rawhide

2010-12-25 Thread Michał Piotrowski
Hi, 2010/12/22 Tom Lane : > Since MySQL AB^W^WSun^WOracle has now declared the mysql 5.5.x release > series to be GA status, I'm planning to push it into rawhide shortly to > replace the 5.1.x series.  Theoretically, this will go pretty smoothly. > > I'm aware of a couple of ABI-level issues: > >