Carol Fields wrote:
> Garrett D'Amore wrote:
>> A couple of quick notes.
>>
>> Shouldn't the Human Readable Output really be Not-An-Interface?
You didn't answer the above question.
>>
>> What are prcat and pwcat? (I see they are in /usr/lib/awk...) Are
>> these user accessible components? Maybe a man page would be helpful
>> (I didn't see references to them in the man pages in the materials,
>> but its possible I missed something.)
>
> The typo referring to /usr/lib/awk/prcat in the ARC case will be
> fixed; it should be /usr/lib/awk/grcat.
> As in Ubuntu and the component package, there is no man page for grcat
> or pwcat.
> grcat and pwcat are documented via `info gawk` (in
> /usr/share/info/gawk.info).
> Both are executable files; grcat generates a printable version of the
> group
> database, and pwcat generates a printable version of the password
> database.
Weird.... seems like these utilities likely have little value in the
"familiarity" point of view (at least for users), but maybe I'm
mistaken. I won't worry about them in any case, though I'd suggest (but
not request) that they be given a lower level of commitment.
>
>>
>> It would be "nice" to have documentation for the various gawk
>> libraries that the project is delivering. (Speaking of which, should
>> those libraries be in /usr/share/gawk instead of /usr/share/awk? I'm
>> guessing that they might not be compatible with stock Solaris awk or
>> nawk....)
>
> The component package (and Ubuntu) installs functions, eg. ctime,
> in /usr/share/awk/, eg. ctime.awk. `info gawk` describes these
> functions.
> Since the name doesn't conflict, these functions will be installed
> in the same directory as the component package.
You misunderstood my concern. My concern is that by having them in a
directory called "awk", some people might expect that they would
*function* with a program called "awk". This is the case on Linux
systems, but it is not the case (or so I presume) for Solaris systems.
Does the path to these libraries get coded directly into the scripts, or
do they wind up using some sort of default path search mechanism (as for
C header files)? If the latter, then perhaps we can rename the path to
gawk, avoid the confusion, and not impact anyone who might desire to use
these files. If the former, then we may be stuck, and I'll just have to
hold my nose (unless someone can take the work to make sure that the
libraries also work with vanilla awk.)
Something to think about, maybe.
-- Garrett
>
> -- Carol
>
>>
>> -- Garrett
>>
>> Don Cragun wrote:
>>> I am sponsoring this case for Carol Fields. It adds /usr/bin/gawk,
>>> /usr/bin/igawk, and /usr/bin/pgawk to the Solaris SFW consolidation.
>>> This case times out on Friday, September 26, 2008.
>>>
>>> - Don
>>>
>>> Template Version: @(#)sac_nextcase %I% %G% SMI
>>> This information is Copyright 2008 Sun Microsystems
>>> 1. Introduction
>>> 1.1. Project/Component Working Name:
>>> Include GNU awk 3.1.5
>>> 1.2. Name of Document Author/Supplier:
>>> Author: Carol Fields
>>> 1.3 Date of This Document:
>>> 19 September, 2008
>>> 4. Technical Description
>>> 4.1. Summary
>>>
>>> This case adds the GNU implementation of awk to the SFW
>>> consolidation for delivery in OpenSolaris/Indiana. GNU awk will
>>> be integrated under the guidelines for /usr/gnu [1].
>>>
>>> This case seeks Patch binding.
>>>
>>> 4.2. Discussion
>>>
>>> GNU awk provides an implementation of the awk pattern scanning and
>>> processing language. GNU awk and Solaris awk are incompatible due
>>> to different parsing. GNU awk offers enhancements over the awk(1)
>>> invocation in /usr/bin. (For example, GNU awk supports the -m and
>>> -W options.) It is expected that developer time will be conserved
>>> by providing GNU awk on OpenSolaris; developers expect the
>>> familiarity of open source tools across platforms.
>>>
>>> A new package, SUNWgawk, will be introduced to deliver the
>>> component. /usr/bin/gawk will be provided; gawk is built by the
>>> component package. /usr/gnu/bin/awk will be a symlink to
>>> ../../bin/gawk. Similiarly /usr/gnu/share/man/man1/awk.1 will be
>>> a symlink to ../../../../share/man/man1/gawk.1.
>>>
>>> The initial version provided will be awk-3.1.5.
>>>
>>> Formatted man pages for gawk and pgawk (gawk.1) and for igawk
>>> (igawk.1) are in this case's materials directory.
>>>
>>> 4.3. Interfaces
>>>
>>> /usr/gnu/bin/awk
>>> (symlink to ../../bin/gawk)
>>> Location Uncommitted
>>> Invocation Volatile
>>> Human-readable output Volatile
>>>
>>> /usr/bin/igawk
>>> /usr/bin/pgawk
>>> Location Uncommitted
>>> Invocation Volatile
>>> Human-readable output Volatile
>>>
>>> /usr/lib/awk/prcat
>>> /usr/lib/awk/pwcat
>>> Location Uncommitted
>>> Invocation Volatile
>>> Human-readable output Volatile
>>>
>>> The following in /usr/share/awk/: assert.awk, bits2str.awk,
>>> cliff_rand.awk, ctime.awk, ftrans.awk, getopt.awk, gettime.awk,
>>> group.awk, join.awk, libintl.awk, nextfile.awk, noassign.awk,
>>> ord.awk, passwd.awk, readable.awk, rewind.awk, round.awk,
>>> strtonum.awk, zerofile.awk
>>> Location Uncommitted
>>> Invocation Volatile
>>> Human-readable output Volatile
>>>
>>> /usr/share/info/gawk.info
>>> /usr/share/info/gawkinet.info
>>> Location Uncommitted
>>>
>>> /usr/gnu/share/man/man1/awk.1
>>> (symlink to ../../../../share/man/man1/gawk.1)
>>> Location Uncommitted
>>>
>>> /usr/share/man/man1/pgawk.1
>>> (hard link to gawk.1)
>>> Location Uncommitted
>>>
>>> /usr/gnu/share/man/man1/igawk.1
>>> Location Uncommitted
>>>
>>> Package containing above interfaces: SUNWgawk
>>>
>>> 5. References
>>>
>>> [1] S. Hahn, B. Smaalders, and R. Orth, PSARC/2007/047: /usr/gnu, 2007.
>>>
>>> [2] S. Hahn, PSARC/2007/049: Including GNU which, 2007.
>>>
>>> [3] S. Hahn, PSARC/2007/048: Include GNU coreutils 6.7.
>>>
>>> 6. Resources and Schedule
>>> 6.4. Steering Committee requested information
>>> 6.4.1. Consolidation C-team Name:
>>> SFW
>>> 6.5. ARC review type: FastTrack
>>> 6.6. ARC Exposure: open
>>>
>>>
>>
>
