[OCF] ocf-shellfuncs standardization - Comments? Objections?

[Nick Stoughton]

> Nick:  If you would consider withdrawing or modifying your bugzilla to 
> the LSB until we finalize our own discussion, that would be much 
> appreciated.

It turns out that my bugzilla comment was a dup of an earlier one, and
has been closed as a duplicate. However, the timeline has this as a
defect to be fixed in release 3.1 (to be published late September 2005
if all goes according to schedule).

Please add your comments to the bug:
http://bugs.linuxbase.org/show_bug.cgi?id=1007

This is a totally open process....you get your comments added to the
bug, and they will be taken into account. Just because I noticed a
problem and filed a bug and proposed a solution, doesn't mean that
others cannot comment on it and propose alternative ways of fixing the
problem.

I'd like some concrete words to put in the base spec; this will be an
ISO standard, and "print a message" is insufficiently precise. How do
you write a test to prove that a message was printed? How do you know
where to look for the message? Language such as "If the XYZ environment
variable is not set, then a message is printed to the standard output"
is acceptable. But the current words are not enough and will be fixed!

-- 
Nick Stoughton      USENIX/FSG Standards Liaison/LSB Editor
nick at usenix.org     (510) 388 1413