Re: pkg/47504: fonts/harfbuzz does not build on (standard) NetBSD 5.0 (native X11)

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR pkg/47504; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/47504: fonts/harfbuzz does not build on (standard) NetBSD 5.0 
(native X11)
Date: Wed, 30 Jan 2013 20:58:23 +0700

     Date:        Wed, 30 Jan 2013 11:55:04 +0000 (UTC)
     From:        "OBATA Akio" <obache%NetBSD.org@localhost>
     Message-ID:  <20130130115504.30FAF63EBDA%www.NetBSD.org@localhost>
 
   |  Put PREFER_PKGSRC.freetype2=pkgsrc on your /etc/mk.conf
 
 I thought something like that would probably work, but it really should
 not be needed - pkgsrc is supposed to support NetBSD 5 (including the 5.0
 series), the logic that determines whether freetype2 is included in the
 base system or not, and whether it is an adequate version, should simply
 determine that the pkgsrc version of freetype2 is needed, and include it,
 without my having to explicitly say so.
 
   | and rebuild whole packages,
 
 So far, all I have built that is likely to be affected (I think) is
 harfbuzz itself, and pango.  I have yet to start on building all the
 packages that depend upon those (on pango really), so the "rebuild" part
 shouldn't really be (very much) needed.   Otherwise I'd need a way to work
 out what packages need to be rebuilt (clearly it is not everything.)
 
   |  or upgrade your userland to 5.2.
 
 For the actual system(s) that I'm using NetBSD 5 on that (or up to 6) is
 actually quite likely - but for building NetBSD 5 packages, that will not
 happen - I always build all packages against the relevant x.0 release
 sets, with no modifications or updates permitted at all (for the purposes
 of package building).  My aim is to guarantee that the binary packages
 will run on any x.y (or x+1.* or later though those matter less to me)
 version of the system (of the correct architecture of course).   I do not
 want to have to have N different sets of packages for NetBSD 5 for 5.0, 5.0.1,
 5.0.2, 5.1, 5.2 ... (and then a whole new set of everything for every new
 NetBSD minor release).
 
 Thanks,
 
 kre