The following reply was made to PR pkg/45483; it has been noted by GNATS.
From: diro%nixsyspaus.org@localhost
To: gnats-bugs%NetBSD.org@localhost
Cc:
Subject: Re: pkg/45483 (x11/libXpm fails on build: can't find -lxcb)
Date: Tue, 18 Oct 2011 21:58:47 -0400
On Wed, Oct 19, 2011 at 01:40:03AM +0000, Matthew Mondor wrote:
> The following reply was made to PR pkg/45483; it has been noted by GNATS.
>
> From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc:
> Subject: Re: pkg/45483 (x11/libXpm fails on build: can't find -lxcb)
> Date: Tue, 18 Oct 2011 21:35:18 -0400
>
> On Wed, 19 Oct 2011 01:20:04 +0000 (UTC)
> "OBATA Akio" <obache%netbsd.org@localhost> wrote:
>
> > You must also set X11_TYPE=modular if you are using PREFER_PKGSRC=yes.
> > Because X11_TYPE=native (default) means you want to use builtin X,
> > so some logics in pkgsrc framework will be confused (naive v.s. pkgsrc).
I will give that a shot now. Strange that it's not been an issue before. I
thought that seeing PREFER_PKGSRC would imply X11_TYPE=modular or at least the
packages would be built with X11_TYPE=modular. Thanks.
> I assume that it's the same issue with pkg/45483, unfortunately.
>
> Timothy, is there any particular reason you prefer to depend on pkgsrc
> duplicates if they are already part of your base system?
I've always had better experiences with running these packages when they're
built locally. IIRC, last time i attempted to use PREFER_PKGSRC=native and
that led to many applications failing unexplainedly, when the pkgsrc builds
worked well for the most part. Also, pkgs in the quarterly stable releases are
almost always newer, more stable, latest features, have (ideally) any security
issues resolved, etc. Moreover, about every 3-4 months, i hack on pkgsrc-wip
and it seems better to have whatever is imported working with what is already
the latest stable in pkgsrc. A lot changes in between the times that i have
available though and i don't keep up with all the changes, some of which
aren't thoroughly documented. I used to do daily builds of pkgsrc-current some
years ago when pkgsrc-current was more stable and report the few bugs that
were found. Sadly, i don't have the time or resources for that anymore and the
state of pkgsrc-current makes that a bit of a chore. That may have been a bit
longer of an explanation than you were looking for.