mary ding wrote:
> I had seen this done before for updates releases. However, we will need
> a Zones developer to see which packages are suitable for the purpose in an
> update release. We also need to know which S10 update releases they are
> target for. If this is done after the real zone upgrade support is
> integrated, it should not be a problem. Both upgrade and without zones
> should work.
IP Instances is targeting S10U4, so the zones upgrade support will be
present.
> As long as the contents is moved to a root package that is also in
> SUNWCmreq and had the proper SUNW_PKG_HOLLOW property, then you can
> fine. You will need to find something where SUNW_PKGTYPE=root and
> SUNW_PKG_HOLLOW=false and it also needs to be in SUNWCrnet cluster.
OK. That handles the cluster issues.
Does the packaging and patch tools handle 'e' files that are moved from
one package to another? Or is the support limited to 'f' files?
Does one have to do something different for 'e' and 'f' files as part of
the move?
For SUNWipfr we don't have a good choice of a target package, since we
don't want to fold that into an existing package for Nevada. One choice
would be to move the SUNWipfr files to SUNWcsr for the S10 update, and
keep them in SUNWipfr (with HOLLOW changed) for Nevada.
But would that cause any issues when upgrading from e.g. S10U5 to Nevada?
Erik
