Andreas Barth <[EMAIL PROTECTED]> writes: > * Manoj Srivastava ([EMAIL PROTECTED]) [061116 05:57]: > > ,---- > > | "Shell scripts specifying /bin/sh as interpreter must only use POSIX > > | features, additionally, they may assume that echo -n .... . Also, > > | they may use test -a/o and the local directive in shell functions, > > | as long as .... If a shell script uses features beyond this set > > | listed, then the appropriate shell must be specified in the first > > | line of the script (e.g., #!/bin/bash) and the package must depend on > > | the package providing the shell (unless the shell package is marked > > | "Essential", as in the case of bash). " > > `---- > > > > This does specify what the scripts may expect, but drops all > > wording from this section regarding what the policy expectation of > > /bin/sh is. > > Sounds good to me. Though (as a non-native speaker) I would rather > reformat it to: > | ... must only use POSIX features, and can: > | - assume that echo -n ... > | - use test -a/o and the local directive
I concur. Please use definition list (bulletin or some suct), to list the items. It's more clear that way. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
