On Tue, Jun 29, 2010 at 10:21:43AM -0700, Gary Pennington wrote:
> Hi,
>
> Small/Quick code review please. Anyone from the zones team who knows the
> context of http://sac.sfbay.sun.com/PSARC/2010/156/mail would be ideal.
>
> webrev:
>
> http://cr.opensolaris.org/~garypen/gate/
>
> workspace:
>
> /builds/garypen/HG/6939693-pkg/gate
>
hey gary,
so, support.c doesn't do anything other than check for inherit-pkg-dir
entries. hence it seems best to just remove the whole program rather
than leave it to do nothing. :)
> I also have a question...
>
> I don't want to putback this change until after I've putback the main change
> for 6939693 to ON. How can I advise people that if they want zones
> to work properly after 6939693, they will need to update the pkg code?
>
> Traditionally, we've solved that kind of problem in the past with an
> update-<whatever> script that you can run to bring your system up to date?
> Does such a script exist, update-pkg, and can I reference it in a
> Heads-Up message?
>
i'd actually recommend putting this change back as early as possible
before the ON change because this change won't actually break anything,
where as if the ON change goes back first, the existing support.c
program will be broken.
wrt update- scripts, that mechanism doesn't really make sense in the
post-ips world. post-ips people use image-update so they update all
their bits in sync. the only people who could get into trouble are
those using onu to update just the ON consolidation. for those, you
could send out a heads up saying something like:
if you onu to ON bits with my fix for 6939693, then you must be
running pkg bits from at least snv_XXX, otherwise zones will be
broken.
ed
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
