mary ding wrote:
> There had been packages that had type "e" and "v" files that moved from
> one package to another in the past. We just need to make sure the
> correct *ph files entries are delivered to handle this. I can help you
> to get this done for Nevada. This had been done before for ON packages.
OK.
>> 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?
>>
>
> We will need to do upgrade testing with S10 updates to Nevada to see
> whether this will work. Before we do this, you have to talk to the ON
> Patch Gatekeeper to make sure that they are willing to do this for S10
> Updates.
Looking at SUNWipfr in more details, I remember it also has /kernel
components, which it makes sense to keep in a HOLLOW package.
Thus for Nevada it makes sense to
- keep SUNWipfr as hollow
- create a new SUNWipfre non-hollow package
- move the non-kernel files from SUNWipfr to SUNWipfre
Sounds like this would need package history files as well.
But for a S10 update, I gather the split into a new package will be a pain.
Thanks for the advice so far.
Erik
