After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to me that is very difficult have a stable version of those databases with current glibc, gcc and maybe os-headers stable defaults (at least on x86 and amd64).

Adding a dev-db/mysql-bin package seems the only short-term viable solution to have those versions of mysql in portage tree. Leaving out all the problems that dependant packages have after mysql 4.1.3 release.

I'm going to writing an ebuild that (maybe using alternatives.eclass) unpack the binary distribuited version of mysql in /opt/ dir and symlink all the programs to paths currently used from the source dist.

any input on how to write it in a way that permit it to be included in the portage tree very apreciated, expecially that from Robin H. Johnson a.k.a robbat2

ciao
Francesco

--
[email protected] mailing list



Reply via email to