ryan nelson wrote:
> Really, though, who can we express EXTREME disappointment to in the 
> opensolaris and indiana community to for being unable to do the basic 
> operation of adding packages to even the first release of Indiana?
> 
> Isn't "ease of package management" one of the big cornerstones of the 
> project?  
> 
> If the first release of Crossbow couldn't ping, or ifconfig, I'd be seriously 
> concerned.  
> 
> really!  what happened?  whatever is was, is it being fixed?  maybe a unit 
> test on "pkgadd" in the nightly build scripts?  please?  Is that a 1.01 
> release feature?
> --
> 
> This message posted from opensolaris.org

This problem appeared in a software drop taken the day before the
final build; we just didn't find the problem until after we
released the ISO.

When your release vehicle is date-driven, certain niceties such
as extensive testing, etc, often go by the wayside.

As soon as we have a fix for this and other issues, we'll push
updated packages to pkg.opensolaris.org and you'll be able to
update your already installed bits.


- Bart


-- 
Bart Smaalders                  Solaris Kernel Performance
[EMAIL PROTECTED]               http://blogs.sun.com/barts
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to