On Wed, Jul 08, 2009 at 02:16:42PM +0100, Darren J Moffat wrote: > However the situation is much harder with cross consolidation flag days, > and this is the case were "update scripts" often come into play. I > think this implies that either all consolidations that ON has build > dependencies from also need a nightly IPS repository or we need a > central nightly IPS repository that all consolidations deliver into.
pkg image-update will update all pkgs whose publishers are enabled. Each consolidation could keep a nightly repo, and if you want to be on the bleeding edge you could just add them all and then image-update. The problem with that, I think, is that initially the publisher of the installed pkgs would be opensolaris.org, and then you'd be changing the publisher all those pkgs to a variety of publishers. I don't know if _that_ is supported by IPS. And it's not clear why one would want to update one consoladation's pkgs but not another's, ... ... which leads me to conclude that a nightly IPS repo would be a good thing. Plus, all redistributable pkgs could be in a public nightly opensolaris repo, say, http://pkg.opensolaris.org/nightly, which would rock. What would be ideal is a way to stack repositories, so one could build a consolidation, send the pkgs to a private repo, and then have IPS look in that repo first, then the common nightly repo that has all pkgs for other consolidations. Instead I expect that engineers would end up creating a locl mirror of the common nightly repo minus the pkgs from the consolidation they are building, then send the built pkgs to that mirror, then image-update from it. Nico --
