will 10.2 break mySQL/Postgres/fink/gimp?

[dsnyder]

I have a bunch of Unix software that I've compiled and/or installed on my iBook under 10.1.5. mySQL, Postgres, the gimp and XDarwin are the four that I use the most and rely on to do my work. Does anyone know if these will continue working if I upgrade to 10.2? I really can't afford the downtime if I have to recompile everything.

Thanks,

David

[Captain Code]

I was wondering this as well since I'm running Postfix and QPopper.

I think that as long as there's nothing in the /Library folder that is installed by the programs you compiled than there probably won't be a problem.

If there is, then you will most likely just need to make install again, and probably not have to compile the apps.

Make sure you back up any configuration files to minimize your down time.

[RiscIt]

I came here looking for help to this problem (no luck btw)

I installed a 10.2 upgrade from 10.1.4 - the MySql user account is dead and I'm pretty sure I need to reinstall the whole thing. Which sux cuz I'm right in the middle of a project.

Now ya know.

[bwanabob]

Heheh..

First rule of a production. Never change the hardware/software/OS until the project is finished.

I've noticed that there is a problem with several open-source packages and GCC 3.x. Depending upon the version of GCC that is used, some packages will not compile. Under 10.1.x, we were using GCC 2.95.2. With 10.2, we now use GCC 3.1. There are dramatic changes between these versions. Usually, this means that the open source package has to have some code modifications before it will compile.

I've been working on the OpenH323 package (to create a "netmeeting-like" package available for OSX), and it will not compile under "Apple's" version of GCC 3.1.

Other opensource packages may suffer this fate.

[Mars]

RiscIt, Jaguar adds a MySQL user of it's own. So, it seems to destroy the permissions on anything that was owned by a "mysql" user before the upgrade.

To fix it, simply chown any files that were owned by your MySQL user to "mysql".

That fixed it for me!

Mars

[RiscIt]

> To fix it, simply chown any files that
> were owned by your MySQL user to "mysql".

Worked great. You rock. Thanks a bunch!

[mkwan]

this may seem to be a dumb question, but how does one do that?

[dsnyder]

Might it be easier to change the uid of the "new" mySQL user back to the uid of the old one (assuming you can figure out what the old uid was). This can be done with Netinfo Manager I believe.