sunanda menon wrote: > > As of now user has to manage the sym links as it's only meant for the > user convenience .The links will always point to the latest version > installed.
The two statements above are contradictory (or at least, appear contradictory unless you're proposing some clever management scheme but if you are, that scheme needs to be documented in the ARC case and today it is not). Today, in SUNWmysql5u, the links are not marked modifiable by users. You could change that in the 5.1 integration (but I don't really recommend that). But if the links are user modifiable (e.g. renamenew or such) then they won't point to the latest version installed (since packages won't overwrite/update them). I recommend keep it simple. The latest (5.1) package contains the links and the point to 5.1 locations. Document for users that anyone writing scripts or such should use the full path to the versioned binary/data they need, that way behavior of their code doesn't change just because an update brings a newer version. The symlinks are there for the convenience of CLI user typing in by hand. [Either that, or look into my earlier suggestion (months ago) of investigating some kind of dynamic version picker (which might be useful for more than mysql).] Basant Kumar kukreja wrote: > > What would happen in following situation : > 1. Install mysql 5.0 : symlinks point to 5.0 Well no, since only one package can own a given piece of filesystem real estate. When 5.1 goes in, it'll own the links and 5.0 won't. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
