> The user could easily change the apache2 symlink if
> it bothers them, and that
> would point to the new version, but would allow your
> entire stack to use the
> runpath you compiler for.
That won't work. It's ad-hoc, and ad-hoc doesn't work if you have several tens
of thousands (yes, you read that correctly) systems to admin. I could perhaps
"solve" this by applying a package over all those thousands of systems that
creates a link for me, but then we get into playing with package and system's
integrity. What if another package already owns that symbollic link? Then I
have to start calling `installf` and `removef`, and come next iteration /
upgrade of Solaris, who knows what I might have broken with my `installf` and
`removef` by "adding" that symbollic link!
If you need to to anything ad-hoc to the system, then it's an architectural
problem, and needs to be handled as such.
Message was edited by:
ux-admin
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
