Re: [Sccs-devel] Installation/documentation discrepancy bug (5.08)

[Joerg S. <Joe...@fo...>]

Bruce Lilly <bru...@gm...> wrote:

> Looking at The Open Group Base Specifications Issue 7 IEEE Std 1003.1,
> 2013 Edition, I see
> "The get utility shall conform to XBD Utility Syntax Guidelines .",
> so "-rsid" would not be permissible per Guideline 6 (sid, as a mandatory
> option argument must be separate from the -r flag), and the page for get there
> shows that.  But that's another issue.

This is a missinterpretation of the standard.

The correct interpretation is that:

1) The man page must document the behavior. If both variants are OK, both need 
   to be mentioned.

2) A utility that supports the (to be avoided) optional option arguments must 
   support the single arg variant.

3) In other cases, the utility may support the single arg variant.

Note that SCCS was converted to use getopt() very late. This happened with the 
changes for SVr4.So e.g. SunOS-5.0 from around 1990 uses getopt() in SCCS while 
SunOS-4.1.X from 1992... still does not use getopt().

Given that it is not POSIX goal to break things, SCCS must support the single 
arg version, but this has to be documented.

The main effective difference between bin/get and xpg4/bin/get is that 
xpg4/bin/get creates an empty (so called g-) file in case you specify a 
non-existent SID, while bin/get aborts only with an error message but with no 
file created.

Note that the NSE enhancements from SCCS actively support optional option 
arguments. But even standard behavior (see admin command) uses POSIX documented 
optional option arguments.

> > Given that the man pages are originally taken from OpenSolaris, I would like to
> > keep the /usr/ccs and /usr/xpg4 paths intact. Yould you be OK with a NOTE that
> > explains that /usr/ has to be replaced by the "installation base" directory?
>
> I suppose so; better would be to make those the default installation
> locations (I
> suspect that there are very few people with anything under /opt/schily
> in $PATH)...

I guess that most people that compile/install will use /opt/schily while dostro 
creators usually chose a different installation base.

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'