S h i v wrote:
> # pkgadd -d . SUNWexpect
>
> Processing package instance <SUNWexpect> from
> </ws/sfwnv/packages/i386/nightly-nd>
>
> expect - Programmed dialogue with other interactive programs(i386)
> 11.11.0,REV=2007.09.28.02.21
> Written by: Don Libes, NIST, 3/23/93
>
> Design and implementation of this program was paid for by U.S. tax
> dollars. Therefore it is public domain. However, the author and NIST
> would appreciate credit if this program or parts of it are used.
>
> YOU MUST OBSERVE ANY AUTHORS' CONDITIONS WITH RESPECT TO
> INDIVIDUAL COMPONENTS PROVIDED WITHIN THIS CODE. SUPPORT
> FOR THE TECHNOLOGIES AND DOCUMENTATION IS NOT PROVIDED
> BY SUN MICROSYSTEMS, INC.
>
> THE TECHNOLOGIES AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT TECHNICAL
> SUPPORT OR WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
> PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
You should take those two paragraphs out of the package copyright file.
They were required by legal for the things on the ccd, but not for
things in sfw, and also incorrectly describe the support situation for
them in sfw, such as it is.
Also be sure to see if you should update it from the sources (since
there may be more info like updated copyrights/dates that should be
there). And we may need to add something after the case is approved
by legal but I'll forward that to you if we do (but you could
look at, say, the automake packages to see what it will be).
>
> Installing expect - Programmed dialogue with other interactive
> programs as <SUNWexpect>
>
> ## Installing part 1 of 1.
> /usr/bin/cryptdir
> /usr/bin/decryptdir
hmm the crypt examples ship eh - we may have to bother export
control too at least to notify them even though they are just
wrappers around 'crypt'.
Make sure that none of these bits conflict with anything
already there in some other package - doesn't look like it
and if you did the pkgadd on a full installation then there
probably aren't or it would have been upset, but do make sure
(this list is also what ARC would like to know).
> /usr/lib/libexpect5.43.a
this .a will be interesting to the arc as well - is there no
way to build it shared easily? static libraries are usually
not allowed (though some could be, I'd argue that the bison/flex
libraries should just be static but could still lose that :)
Mike
