On Sat, Sep 27, 2008 at 6:09 AM, James C. McPherson
<James.McPherson at sun.com> wrote:
> I've got the list of patches applied, courtesy of an email
> to Nick a few days ago. I include it here, and I'll put it
> on blogs.sun.com/jmcp as well.
I have typically installed Sun Studio into an alternate root with
something like:
./batch_installer -R /opt/studio12
This allows me to maintain (i.e. patch) the installation long after I
have whacked the installation that has the associated /var/sadm/*
metadata. Anyway, starting from snv_93 I found that patchadd fails to
apply patches to an alternate root (lost the exact error message) due
to it not always using the altenate root in its attempts to look for
the package metadata. This can be worked around by:
Install (missing the option to accept license agreement)
zfs create -o mountpoint=/opt/studio12 rpool/studio12
./batch_installer -R /opt/studio12
It pukes after it installs 168 packages - presumably when it invokes
patchadd or similar. The packages are left installed.
Create symlinks to work around bug in patchadd (if you can imagine).
cd /var/sadm/pkg
ln -s /opt/studio12/var/sadm/pkg/* .
Install patches
cd /tmp/patches
patchadd -R /opt/studio12 -M `pwd` *
Verify that nothing changed in /:
find / -mount -newer /var/sadm/pkg
Clean up symlinks
cd /var/sadm/pkg
ls -l | grep /opt/studio12 | nawk '{print $(NF-2)}' | xargs rm -f
Create /opt/SUNWspro symlink
cd /opt
rm SUNWspro
ln -s studio12/opt/SUNWspro SUNWspro
Flipping between studio 11 and 12 can be done via a symlink (or PATH
with a forgiving build environment).
--
Mike Gerdts
http://mgerdts.blogspot.com/
