John Plocher wrote:
> Joseph Kowalski wrote:
>> Halton Huo wrote:
>>> 2. no man pages for SUNWguile
>>>    community do not have, only have info
>>> 3. no man pages for SUNWautogen
>>>    ???community have
>>>   
>> Good catch.
>>
>> I would expect there to be "vestigial" man pages as per our FOSS 
>> integration process.
How many precedents would you like?
>
> Without "vestigial man pages", does this imply:
>
>     Can't go into SFW (but might go into the Companion CD/Experimental 
> repo)?
It is a requirement to be delivered as part of Solaris.  Last I looked. 
SFW was only
different (from ON) in that it wasn't bound to the Makefile standards 
and "quiet
build" requirements of ON.
>
>     Can't go into a Minor release of SFW?
Doesn't matter what type of release.  Can't go into Solaris.
>
>     We need to change the rules for what goes into SFW?
Sure.  Everybody likes less work.  But the current rules are the rules.

BTW: I made a couple of "vestigial man pages".  Takes 30 minutes on the
very out side.
>
>     Case gets rejected/deraile/TCR's to make work creating man pages?
Yes.  They have been.
>
>     Case gets told to go fetch an "info to man converter" rock?
>
>     ...?
What the &^#$#*&$ ???

Read what I wrote.  (and I'll try to provide more details that anybody
should be able to understand).

>
>   -John
As ARC coordinator, you should not be surprised about this. See:

    PSARC/2000/488  Solaris/Linux Commands Compatibility      Bick 
Torrejon         unset
    closed approved 05/02/2001            Joseph Kowalski

 From the opinion:

     1.   A single manual page shall be  made  available  as
          part  of  the  base documentation set which can be
          located via the  default  MANPATH  describing  the
          intent  of the ``sfw'' interfaces and what changes
          need to be made to a users environment  to  access
          them and their associated documentation.

Need I say more?

Probably:

A typical "vestigial manpage" would have:

    NAME

       <as usual>

    SYNOPSIS

       <as usual>

    DESCRIPTION

       >>> a textual pointer to where the documentation lies<<<
       >>> probably in info pages, but could be pdf, html,... <<<

    ATTRIBUTES

       <as usual>

The ATTRIBUTES part is **very** important.
Otherwise, how does the reader know the
"Interface Stability"?

- sigh,

- jek3




-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080512/13fa47f8/attachment.html>

Reply via email to