Hi Ritu, > Shall appreciate your feedback on this email. > > Is it ok to install 32bit mysql under /usr/mysql/32bit and 64bit under > /usr/mysql/64bit. > > I understand that this is different from how Solaris libraries are > distributed but if we twig the way MySQL is usually installed, it will > not go well with the users of MySQL (as they will be all confused > to not > find the required binaries in its place and also to find redundant sym > links to different directories)
The standard format for most MySQL binary installation packages is for the files to be installed into /usr/local/mysql-5.0.45 and then for a symlink to be created that links /usr/local/mysql to the appropriate version specific directory. We do that to allow users to upgrade to a new version without hosing their old one. There are some platforms on which, for historical reasons, we do this different (Solaris is one); the current PKG installs use the /usr/ local target but a known bug hat I reported recently sets the the data directory to the wrong location. I think installing into different 32-bit/64-bit directories may be confusing, but if we have to go that way, then I would suggest we install to 32-bit/64-bit specific directories and then provide a single link (/usr/local/mysql) to the location the user wants to use. That should prevent users having to learn a completely different structure, while still allowing the 32-bit/64-bit specifics if they need them. > I think we should install MySQL the way it is usually installed . > We can > change the installation directory, the data and log directory but > if we > try to change the location of files inside the install area, it > will all > become very messy and confusing. I agree here. I'd much rather see both the 32-bit and 64-bit installs basically end up in the same place. I think it unlikely that both32-bit and 64-bit would be installed at the same time, but if we have to support it, I'd rather we did it in a way that allowed users to use the 'trditional' layout if they want. > On a seperate note, do we have to bundle both 32bit and 64bit of MySQL > in webstack ? Based on the other thread "Database 32bit and > 64bit" , it > appears to me that the requirements is just to integrate 32bit. I agree here too - at the current time 64-bit is probably a moot point. Although we support the 64-bit version there are some known issues with the 64-bit builds, particularly with the widely known compatibility issues of linking 32-bit and 64-bit libraries. Not to mention that external tools do not currently operate with 64-bit. C/ ODBC is known to fail on 64-bit/Solaris, and we already know of an issue with Perl and the DBD::mysql module on Solaris with 64-bit libraries. I haven't checked the recent PHP builds, but I understand these may have a similar issue. MC (also mc at mysql.com) -- Martin 'MC' Brown, mc at mcslp.com Everything MCslp: http://planet.mcslp.com