Peter Memishian wrote:
> 
>  > >      * READMEs and other textfiles that aid in understanding the source.
>  > >        (Exceptions for these are automatically granted, provided the 
> files
>  > >        end in ".txt".)
>  >
>  > What about text files like manual pages ? Currently we ship the
>  > _original_ ksh93 manual page to have this part of the documentation
>  > exactly 1:1 in sync with the code (while the official Solaris ksh93
>  > manual page is a derived version with various changes and usually laggs
>  > behind the actual status of the code). Does this fall under the same
>  > category as the "text files" waiver or is a seperate explanation needed
>  > ?
> 
> I think that probably needs a separate explanation.

What about saying "... an exception is granted if the manpage(s) in the
sourcetree is/are maintained[1] and the Solaris versions of the
manpage(s) is/are significantly different" ?

[1]=Where "maintained" means that in ksh93's case David Korn changes the
manual page for each change in behaviour of the code (e.g. the manual
page history log could be used to track changes (while
usr/src/lib/libshell/common/RELEASE tracks the fine-grained changes to
the code (including bugfixes))).

>  > >      * Source subtrees that will likely be resynched with an upstream 
> entity
>  > >        (e.g., sqlite).  (This exception does not extend to unused build
>  > >        infrastructure: upstream Makefiles and other unused build files 
> are
>  > >        forbidden since they are a hazard to those maintaining ON's actual
>  > >        build infrastructure.)
>  >
>  > What about sources which are currently not used but will be used later ?
> 
> By itself, that's not an adequate justification -- but the example you
> cited would be covered as part of the "upstream entity" exception.

Ok...

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) [EMAIL PROTECTED]
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to