Amanda Waite wrote: > > >Define it this way instead MYSQL_PATH=/usr/mysql and > >MYSQL_LIB=$(MYSQL_PATH)/lib/mysql > > I think this would lead to some ambiguity and potential problems. What > if you were to update MySQL to 5.2?. I might no longer be able to > predict if Lighttpd will be linked against MySQL 5.1 or MySQL 5.2, it > would all depend on the order that the two MySQL's were built. I think > that being specific is better.
It won't be ambiguous, the 'latest' link is always the latest one. Whether you want the 'latest' or a specific version depends on what the dependencies are. In theory, if you are depending on MySQL interfaces which are classified Uncommitted or better, you can know there will not be an incompatible change as MySQL goes from 5.1 to 5.2 (for instance), so you're better off depending on 'latest'. If you're depending on Volatile interfaces specific to 5.1 then you need to hardcode 5.1. Of course, if that is the case then there will be a problem eventually when 5.1 is removed. In practice the build already has other hardcoded areas which need to be changed manually as MySQL version upgrades (pkg deps, build component deps). Just wanted to make sure you're deciding to hardcode 5.1 use for the right reasons. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
