pkg/42507: math/R-DAAG generates non-fatal error during POST-INSTALL

[kre%munnari.OZ.AU@localhost]

>Number:         42507
>Category:       pkg
>Synopsis:       math/R-DAAG generates non-fatal error during POST-INSTALL
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 23 17:10:00 +0000 2009
>Originator:     Robert Elz
>Release:        NetBSD 4.0 / i386   (pkgsrc current as of 2009-12-22)
>Organization:
        Prince of Songkla University
>Environment:
System: NetBSD jade.coe.psu.ac.th 4.0_STABLE NetBSD 4.0_STABLE 
(JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008 
kre%jade.coe.psu.ac.th@localhost:/usr/obj/4/kernels/JADE i386
Architecture: i386
Machine: i386
>Description:
        During its POST-INSTALL script actions, a build of math/R-DAAG
        (R-DAAG-1.01) issues an error message about being unable to create
        a file (directory non-existant)   This doesn't stop the package
        from (aparently) building correctly, but I suspect that the
        resulting package isn't really as intended.

>How-To-Repeat:
        I use pkg_comp with libkver and NetBSD 4.0 release sets installed
        (with X11_TYPE=modular instead of the x* sets).   For this PR, the
        most likely relevance of any of that is that the pkg_comp sandbox
        starts empty (almost) - only the package itself, and its dependencies
        are installed (and base NetBSD, without X unless X is a dependency).

        In that environment, the build of math/R-DAAG reports ...

=> Running POST-INSTALL script actions
R-DAAG-1.01: rebuilding R package indices and help files
/pkg_comp/obj/pkgsrc/math/R-DAAG/4x/.pkgdb/+INSTALL: cannot create 
/usr/pkg/lib/R/doc/html/search/index.txt: directory nonexistent
=> Registering installation for R-DAAG-1.01
        [...]

        In /usr/pkg (in the sandbox) /usr/pkg/lib/R/doc/html exists,
        but /usr/pkg/lib/R/doc/html/search does not.

>Fix:
        Most probably, the POST-INSTALL script needs to mkdir the directory
        beforce attempting to install that file.  That or if the file isn't
        really needed, then skip attempting to install it...   If the mkdir
        is added, then a revbump will be required.   I'm not sure whether
        a file added by a POST-INSTALL script would need rto be added to PLIST.