On Thu, Aug 06, 2009 at 10:56:52AM -0700, Glenn Lagasse wrote:

> * Aaron Epps (epps.aaron at mayo.edu) wrote:
> > What is it and why isn't it installed by default? After doing a clean
> > install of OpenSolaris 2009.06 I'm immediately told to install this
> > update; when I do it creates an entirely new boot environment. What
> > happens when I install the "entire" package? Do I really need a whole
> > new boot environment to install this package?
> 
> So, first it is installed by default.  What you're seeing is that we had
> to backpublish a fix to the entire package in order to fix a potential
> upgrade issue.  Entire doesn't contain any packages (merely constrains a
> set of packages to specific version).  You don't need to create a new BE
> to upgrade entire in this case.  You could do:
> 
> pkg install entire
> 
> and that will install the new version of entire.

In general, though, that's quite dangerous, as if it moves the constraints
on system packages forward such that things like libc get updated, you run
a reasonable chance of blowing your system to kingdom come.  Be
extraordinarily careful whenever you manipulate entire -- generally run
with -nv first, to see exactly what will be updated.

Soon we should have mechanism to prevent you from toasting your system in
this way, but it's not there yet.

Danek

Reply via email to