pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/48919



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

From: David Sainty <dave%dtsp.co.nz@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Philip Miller <sighoya%gmail.com@localhost>, 
pkg-manager%netbsd.org@localhost, 
 gnats-admin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/48919
Date: Thu, 26 Jun 2014 13:15:02 +1200

 On 26/06/14 00:10, Philip Miller wrote:
 >   >   > From: David Holland <dholland-pbugs%netbsd.org@localhost>
 >   >   > To: gnats-bugs%NetBSD.org@localhost
 >   >   > Cc:
 >   >   > Subject: Re: pkg/48919
 >   >   > Date: Wed, 25 Jun 2014 06:15:03 +0000
 >   >   >
 >   >   >   On Mon, Jun 23, 2014 at 01:20:00PM +0000, Philip Miller wrote:
 >   >   >    >  >> What do you see for: make show-var VARNAME=X11_TYPE
 >   >   >    >  native
 >   >   >    >  and another variable
 >   >   >    >  X11BASE=/usr
 >   >   >
 >   >   >   If you're using native X, which includes freetype2 and fontconfig, 
 > you
 >   >   >   shouldn't also be using the pkgsrc ones; this causes confusion.
 >   >   >
 >
 >   I don't see the solution to install xorg-modular, cause the option of
 >   X11_TYPE=native exists. Some Time ago, I have build graphical apps on
 >   netbsd with native xorg, and there were no problems. There must be a
 >   solution.
 >
 
 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.
 
 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.
 
 > 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?
 
 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
 


Home | Main Index | Thread Index | Old Index