[indiana-discuss] new BE for just two upgrades

[Sanjay Nadkarni]

On 07/10/09 15:04, Frank Ludolph wrote:
> Matt Ingenthron wrote:
>> Calum Mackay wrote:
>>> out of interest, what exactly is the problem with having more BEs 
>>> than you think you need?
>>>
>>> ZFS is going to look after the space; I suppose keeping track of 
>>> what they all are is the issue?
>>
>> Shawn's answer covers the needed functionality, but the issue is that 
>> there are some classes of things you don't want to have to go create 
>> a new BE for.  For instance?  I was working on building some 
>> software, noticed the new SunStudioExpress, went to install it, and 
>> inadvertantly, through the GUI, went down the image-update path.
>>
>> A new user may assume that's the only path, and rebooting to use a 
>> newer compiler is pretty silly.
>>
> If you are referring to the Pkg Mgr GUI, there is an "Install/Update"" 
> button just to the right of the "Update All". However, I know that 
> users, myself included, can miss seeing even an adjacent button title. 
> Perhaps reversing the order would cause most people to see the 
> "Install/Update button first, though since it would be disabled until 
> the user has at least clicked on a package, some users will still pass 
> over it and click Update All...
I concur with Frank having just run into this.  I had selected 
OpenOffice pkg to download and  accidently clicked on update all. I 
caught my error when it warned about creating a new BE, but a newbie 
would not know this.

-Sanjay

>
> Frank
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss