empowering
Verified User
DA and smtalk... can you NOT _NOT_ *NOT* force install mysql rpms per your build script. With a new install I tell mysql in the options.conf to not install the mysql rpms.
before running setup.sh. I have the setup.sh run custombuild and perform the install automatically (which I'm not going to detail here).
yet mysql rpms not only get installed BUT you perform a force install with mysql rpms already there (not the RH/CentOS) RPMs that are also newer then your rpms. So I have two sets of rpms! My mysql rpms there were pre installed and then DA's:
Why is my options.conf not working? Can you also stop doing things like forcing rpms to get installed and do things the proper method if you are using rpms!!! As I've stated previously all of this makes it very hard to automate and the world does not revolve around DA's 'build' script.
Code:
mysql=5.0
mysql_inst=no
mysql_backup=no
before running setup.sh. I have the setup.sh run custombuild and perform the install automatically (which I'm not going to detail here).
yet mysql rpms not only get installed BUT you perform a force install with mysql rpms already there (not the RH/CentOS) RPMs that are also newer then your rpms. So I have two sets of rpms! My mysql rpms there were pre installed and then DA's:
Code:
[root]# rpm -q -a | grep -i mysql
MySQL-devel-community-5.0.51a-0.rhel4
MySQL-client-community-5.0.51a-0.rhel4
MySQL-client-community-5.0.41-0.rhel4
MySQL-shared-community-5.0.41-0.rhel4
MySQL-server-community-5.0.51a-0.rhel4
MySQL-shared-community-5.0.51a-0.rhel4
MySQL-server-community-5.0.41-0.rhel4
MySQL-devel-community-5.0.41-0.rhel4
Why is my options.conf not working? Can you also stop doing things like forcing rpms to get installed and do things the proper method if you are using rpms!!! As I've stated previously all of this makes it very hard to automate and the world does not revolve around DA's 'build' script.
Last edited: