Mike Gerdts wrote:
> Why take this approach rather than changing or overriding the
> SUNW_PKG_ALL_ZONES attribute on SUNWsolnm? It seems as though the
> approach taken will make it so that the package version doesn't match
> up with the release and pkgchk will complain about /etc/release in
> non-global zones that have been updated to a newer release.

Honestly, it just didn't occur to me, but your general comments
are correct and it would be better to do what you are suggesting.

> Without knowing any of the back story and assuming that changing
> SUNW_PKG_ALL_ZONES on an already installed package is really bad to
> do, it seems as though this could be better handled with a hook here:

Yes, we cannot change these attributes once a pkg has been released.

> usr/src/lib/brand/native/zone/sw_support.c
>   1115
>   1116                  } else if (strcmp(buf, SUNW_PKG_ALL_ZONES) == 0) {
>   1117                          infop->zpi_all_zones = B_TRUE;
>   1118
> My thought is that if the package name is SUNWsolnm,
> infop->zpi_all_zones should be B_TRUE.

I will file a bug to add this pkg to the dependent list whenever there
are other pkgs on the list.

zones-discuss mailing list

Reply via email to