Laszlo (Laca) Peter writes: > Sounds good to me. > Two questions: what's adequate stability
It depends on the situation. In general, it means that there's some useful subset (perhaps the entire set) of functionality that can be nailed down "forever." It won't ever change, either because we're just not going to change it, or because the community doesn't want to change it, or because we promise to provide compatibility patches if the community loses its collective wits. It's not something that can be discussed well in the abstract except to say that it's enough stability for some well-engineered application to depend on it. To say more than that requires an actual case to consider and an architectural review. > and what do you do with > commands and libraries with inadequate stability? > > Leave them in > /usr/gnu? Not ship them? Yes, /usr/gnu. Moving things around when stability changes doesn't seem like a great plan to me. It hasn't worked out well so far. That means predicting the right level when you put it in is very helpful. -- James Carlson, KISS Network <[EMAIL PROTECTED]> 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 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
