Re: CVS commit: pkgsrc/pkgtools/bootstrap-mk-files

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2013-09-03 at 15:02 BST, Jörn Clausen wrote:

> The first package I build after bootstrap is devel/rcs. This now fails with
> 
> => Automatic manual page handling
> Full pathname symlink
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/bin/rlog'
> is target of 
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/bin/rcslog'
> - adjusting to `../bin/rlog'
> Full pathname symlink
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/man/man1/rlog.1'
> is target of 
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/man/man1/rcslog.1'
> - adjusting to `../../man/man1/rlog.1'
> pkg_create: can't stat
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/share/info/dir'
> => Creating binary package
> /pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.packages/rcs-5.9.0nb1.tgz
> pkg_create: can't stat
> `/pkgsrc/source/pkgsrc/devel/rcs/work.pkgsrc-i86/.destdir/usr/pkgsrc/20130903/share/info/dir'
> pkg_create: lstat failed for file share/info/dir: No such file or directory
> *** Error code 2
> 
> Stop.
> 
> 
> The same source builds successfully, when I use an older pkgsrc
> userland that still uses install-sh instead of bsdinstall (which
> causes devel/rcs to revert in some places to ../build-aux/install-sh,
> btw). I can't pinpoint the place where things go wrong with the newer
> infrastructure. The directory share/info is created in both cases,
> with identical permissions.

This is possibly related to the PKGINFODIR change I committed to
bootstrap earlier in August.  If you were using a custom setting then
you will need to replicate it with --pkginfodir (or change mk.conf
after bootstrap).

Alternatively, if the info generation tools have hardcoded install-sh
then they will need to be rebuilt after switching to bsdinstall.

> I haven't found a reason for switching to bsdinstall, just the fact
> that you did it. At the moment this looks to me like a case of "if it
> ain't broken..."

The bsdinstall commit log explains it further, but essentially the
install-sh script cannot handle files with spaces in them, which
breaks a reasonable number of packages.  bsdinstall fixes this, and
will be faster / more future-proof.

I've booted up a Sol9 machine and will look at fixing the err.h
failure.  If you aren't bothered about the packages that install-sh
cannot handle, then you can just comment out the use_bsdinstall=yes
line in bootstrap and revert to the previous behaviour.

Cheers,

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com