Don Cragun writes: > I see that now. As you have probably noticed, I'm getting the ARC mail > in digest form. The digest that said this case had been approved didn't > hit my inbox until after the PSARC meeting Wednesday. When I raised the
I believe you were still on the line when we derailed and voted. That was the actual approval -- derailing converts the fast-track to a full case, and a vote causes it to close. > issue during the meeting, it seemed to me that I had raised the issue of > optional option-arguments and didn't see any reaction to the issue > before the case disappeared from the agenda. I was just asking for > clarification on what had been decided. What was decided was that the CLIP infraction (regarding the requirement for equivalent short options) was insignificant compared to the GNU compatibility issue. The whole point of the project is to allow users to specify "familiar" GNU options to 'ls', and have them just work, rather than forcing people to reach for /usr/gnu/bin/ls, which (sadly) doesn't support Solaris features. Specifically, the vote was on allowing the case to go forward as originally specified and without requiring a man page warning, as the original specification did _not_ contain ambiguous constructs, because the only optional option argument was a strict "--color[=WHEN]" string, with no possibility of "--color WHEN". (In fact, I'd go so far to say that to the extent that CLIP might call the former an ambiguous construct, it's wrong. But that's a separate case.) If this case changes to include ambiguous constructs, then that'd be a material change, and we'd have to revisit. > is on the internal agenda. Furthermore, as I remember the internal > agenda, there were links directly from the agenda to the case > directories for all of the fast tracks. There are no links in the > external agenda. I'm getting better at typing in the web addresses on > the fly, but it is a lot slower than the direct links. I've agreed before that something needs to be done about this. I still do. There's obviously more infrastructure work to be done. I don't know of a schedule for it. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
