David.Comay at Sun.COM writes: > > Unfortunately, SUNWastdev is in SUNWCdev -- it's intended to be > > delivered to customers who can't actually use it. > > > > Yes, in a better world, I think SUNWastdev is exactly where such bits > > would go. > > I think SUNWastdev is the right place for these (or at least, the AST > related ones) and that SUNWastdev is built but not actually shipped as > part of the product. That way, other consolidations or those needed to > create build servers can use them.
The project team has been adamant about not just shipping SUNWastdev, but keeping it in the SUNWCdev metacluster, even though it can't actually be used by ordinary developers working on Solaris. I don't think changing that package to be unshipped (the right solution, in my opinion) will fly. > When the interfaces in question are upgrade, the *.so links and the > lint libraries can be migrated to the appropriate core packages. Yes; that's what's expected. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
