On 12/20/11 10:52, Robert Thurlow wrote:
More generally, are there any best practices? I am trying to do something pretty vanilla - have a project gate that I and others can install from. Thanks,
In general, updating to newer bits just works. The packaging system will following the constraints encoded in the packages; one of those constraints is that packages that comprise a single consolidation cannot be from mixed builds.
So what would be the syntax for asking pkg to install my own bits, that show up marked with "0.5.11-0.175.0.0.0.2.18011"?
pkg update [email protected] will update the your OS to the specified version. The various consolidations have incorporation packages that specify the various version of packages that were built & tested together; the "entire" package by default locks all the consolidation incorporations together so that one is running components that are all from a particular build. Removing entire allows one to pick which version of the consolidations are used together; note that one is still subject to any additional dependencies specified in the individual packages, so attempting to mix bits too far out of sync will result in error messages. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with Mercurial than with Thunderbird." "Civilization advances by extending the number of important operations which we can perform without thinking about them." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
