Has any more thought been given to an install-time solution for the multiple-versions problem? This could either be a special action, or it could be handled by an SMF service that updates the symlinks in response to a config file installed by the package. Since I haven't heard anything about this topic in a while, I assume this is on the back burner for now?
--chris > Here's a sketch of an example implementation: > > Both prog13 and prog14 packages include a new kind of action. > Let's call it the VEREXEC action. :-) The argument would be > the pathname of the real binary. The symlink would be hardwired > to always go in /usr/bin. (I think the only real problem being > solved here relates to the /usr/bin directory, so it's okay > to hardwire that directory.) Any package with a VEREXEC > action ending in "foo" would conflict with a package that > delivers any file/link/directory to /usr/bin/foo. > > I don't really know the best way to implement this in pkg, > it could just be a semantically active keyword/flag attached > to the action that creates the real binary. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
