Hello.
It is recommended to use precompiled binaries in most cases. MySQL has a very flexible system of parameters which you could change through different ways. If you want to use this server as dedicated database server, probably the solution exists (I mean integrating MySQL binaries without breaking apt's database). But if you want to use other programs which requires MySQL shared libraries the problem becomes harder. [EMAIL PROTECTED] wrote: > Hi, > > I've been successfully using mysql 5.0.x on my win32 development machine. > > I would like to install it on a server running stable Debian. Unfortunately, > there are no .deb packages for the MySQL 5.0 series. > > I have tried to use the linux precompiled binaries but my debian complains > about > not being able to connect using "/var/run/.../mysqld.sock" and the > "/etc/init.d/mysql start" script will tell me something went wrong. > I have accidentally deleted "/etc/mysql/debian-start" and replaced it with an > empty file :(. > > Now, what I would like to do is to either > 1) use the precompiled binaries without breaking apt's database (ie > overwriting > the files that already exist) and using canonical debian path conventions. > 2) compile by myself, but I *really* need some help with all the options > ./configure provides, in order, again, to use the debian patch conventions. > > thanks in advance, > Phil > -- 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]
