Re: pkg/48919

[David Sainty <dave%dtsp.co.nz@localhost>]

On 27/06/14 08:30, Philip Miller wrote:
> The following reply was made to PR pkg/48919; it has been noted by GNATS.
>
> From: Philip Miller <sighoya%gmail.com@localhost>
> To: gnats-bugs%NetBSD.org@localhost, David Sainty <dave%dtsp.co.nz@localhost>
> Cc:
> Subject: Re: pkg/48919
> Date: Thu, 26 Jun 2014 22:27:22 +0200
>
>   >
>   >   It is necessarily the case that X11_TYPE=native cannot be guaranteed to
>   >   work forever.  If, for example, libX11 grows a new feature F, and then
>   >   application A requires feature F, then A cannot be built with
>   >   X11_TYPE=native until the native X11 libraries are updated (not just
>   >   patched, which is more commonly what happens with base system updates).
>   >   Pkgsrc will eventually outgrow the native system unless it has a more
>   >   extreme upgrade.
>   >
>   Does this mean, that the native support is thrown out in future?

Not that I'm aware.  But the distance between a system's native X and 
the packages in Pkgsrc will normally increase over time as the base 
system ages, so sometimes you might find that it's easier to switch to 
modular X at a certain point in time.

>   >   That might be an aspect of the problem here, where perhaps the
>   >   up-to-date version of cairo is demanding a later version of fontconfig
>   >   than is on the native system.  But the root cause of builds failing is
>   >   that native freetype2 is not being handled properly, and any package on
>   >   your system that attempts to use freetype might run into the same trouble.
>   >
>   I think too, cause the native and the pkgsrc version of freetype are the
>   same, in may case.

Ah.  Yes, in your case the distance is probably not in terms of the 
versions but in terms of dependencies.  Still, you might just be the 
first of many in this position, if the various distributions start using 
the png support in freetype in the base.  Which Linux distribution are 
you using?

>   >   > From: Thomas Klausner<wiz%NetBSD.org@localhost>
>   >   > Subject: Re: pkg/48919
>   >   > Date: Thu, 26 Jun 2014 00:36:01 +0200
>   >   >
>   >   >   I'm against adding builtin support for more packages in general, and
>   >   >   for png in particular as well, since pkgsrc contains the latest
>   >   >   version and many Linux distributions are far behind. This will just
>   >   >   lead to more bug reports...
>   >   >    Thomas
>   >
>   >   With that in mind, I think we can't safely make use of this system's
>   >   native freetype.  That suggests we should go in the other direction and
>   >   not try to use native freetype in the first place.  Possibly the
>   >   freetype2/builtin.mk should detect if native libraries used libpng, and
>   >   inhibit using native libraries in that case?
>   This sounds complicated. Which native libraries use libpng in my case?

The only one I know for sure is freetype2.

>   >   Philip, if you prefer not to use modular X entirely, you could
>   >   presumably resolve at least the build problems manually in a more
>   >   fine-grained manner via adding to mk.conf:
>   >
>   >   PREFER.freetype2=pkgsrc
>   >   PREFER.fontconfig=pkgsrc
>   >
>   This does'nt help, cause fontconfig fails to build.
>   
>   checking for FREETYPE... no
>   configure: error: Package requirements (freetype2) were not met:
>   
>   Package 'libpng', required by 'freetype2', not found
>   
>   Consider adjusting the PKG_CONFIG_PATH environment variable if you
>   installed software in a non-standard prefix.
>   
>   Alternatively, you may set the environment variables FREETYPE_CFLAGS
>   and FREETYPE_LIBS to avoid the need to call pkg-config.
>   See the pkg-config man page for more details.
>   *** Error code 1

That's surprising.  Did you do a completely clean build?  Perhaps the 
preference is being overridden by the X11 type...