Robin H. Johnson ha scritto:
On Tue, Feb 22, 2005 at 01:55:57PM +0100, Francesco Riosa wrote:
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
I'd say it should be mutually exclusive of the source-built version
(DEPEND=!dev-db/mysql). See about putting it's bindir into the PATH
instead of messing around with symlinks. However I think it should use
the same /var/lib/mysql for it's data directory.
Ok, I'll discover how to add a /etc/env.d/98mysql
By default it should provide the stock binaries, if USE=max, then
provide the mysql-max binaries, and if USE=debug, instead provide the
debugging binaries.
IUSE="max debug innodb berkdb selinux utf8 perl ruby"
with "max" and "debug" mutually exlusive,
"innodb" "berkdb" "selinux" "utf8" modifying the my.cnf file
"perl" "ruby" operating on RDEPEND
?
--
[email protected] mailing list
