we are specifying the following in the spec file so that the package gets installed in global zone and in all child zones.
SUNW_Pkg_AllZones: true
SUNW_Pkg_Hollow: false
SUNW_Pkg_ThisZone: false
However the package fails to install in global zone and the error that is shown is as below
pkgadd: ERROR: The package <packagename> has <sunw_pkg_allzones> = true and <sunw_pkg_thiszone> = true: the package may set either parameter to true, but may not set both parameters to true. NOTE: if the package contains a request script, it is treated as though it has <sunw_pkg_thiszone> = true
pkgadd: ERROR: unable to install package <packagename></packagename></sunw_pkg_thiszone></sunw_pkg_thiszone></sunw_pkg_allzones></packagename>
If we specify the following values in spec file
SUNW_Pkg_AllZones: false
SUNW_Pkg_Hollow: false
SUNW_Pkg_ThisZone: false
the package gets installed only in global zone only but not in child zone. Just wanted some clarification as to if these parameter values are indeed supported by pkgbuild. Also some pointers on how we can accomplish installing on global and child zones using pkgbuild would be really helpful.
somehow the parameters got missed above, pasting it again
pkgadd: ERROR: The package [packagename] has SUNW_PKG_ALLZONES = true and SUNW_PKG_THISZONE = true: the package may set either parameter to true, but may not set both parameters to true. NOTE: if the package contains a request script, it is treated as though it has SUNW_PKG_THISZONE = true
pkgadd: ERROR: unable to install package
Looks like SUNW_PKG_THISZONE parameter is set to "true" if there are "request" scripts/sections in the spec file and that is what is causing the issue here. Is "request" script/section allowed by pkgbuild tool in spec file? if not is there any alternate arrangement for the same.
Kindly close this defect as it seems to be working as per design. Thanks.