Re: pkg/53751: code blocks fails to build

[<rnestor%tx.rr.com@localhost>]

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

From: <rnestor%tx.rr.com@localhost>
To: pkg-manager%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost, gnats-bugs%NetBSD.org@localhost, 
	gnats-admin%netbsd.org@localhost
Cc: David Holland <dholland-pbugs%netbsd.org@localhost>
Subject: Re: pkg/53751: code blocks fails to build
Date: Tue, 1 Jan 2019 16:04:14 -0500

 Seems that one of the many benefits of the pkgsrc system is that a library or sub-component which is used in multiple packages only needs to be built once for use by all, but this can also be an Achilles Heel.  If the library or sub-component is upgraded and the API or similar isn't kept backwards compatible then some packages which rely on it that haven't upgraded may become unbuildable and unusable.  Is there an option in the pkgsrc system that permits a package to import and build it's own local copy of an older library or sub-component that it depends upon?  If so that might solve the problem with Codeblocks without having to move wxGTK back to GTK2, at least until Codeblocks is upgraded to use the wxGTK/GTK3 interface.
 
 However, in this case the real source of the problem may be in wxGTK rather than in Codeblocks as Codeblocks can be build and linked with wxGTK that was built with GTK3, but at run time it complains that GTK2 and GTK3 symbols can't both be in the same image.  It would seem that if wxGTK can build with both than shouldn't it be intelligent enough to know which GTK calls it should be using?
 
 -bob
 
 ---- David Holland <dholland-pbugs%netbsd.org@localhost> wrote: 
 > The following reply was made to PR pkg/53751; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-pbugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: pkg/53751: code blocks fails to build
 > Date: Tue, 1 Jan 2019 18:44:27 +0000
 > 
 >  On Sat, Dec 29, 2018 at 10:35:01AM +0000, Benny Siegert wrote:
 >   >  >  You can make it set PKG_FAIL_REASON if not (by checking
 >   >  >  PKG_BUILD_OPTIONS) but I don't think there's any way to express the
 >   >  >  dependence directly or get the system to build wxgtk with the option
 >   >  >  automatically.
 >   >  
 >   >  Would it make sense to flip the wxGTK30 default to gtk2, so that at
 >   >  least codeblocks can be built in the bulk builds?
 >  
 >  I don't know. I imagine there was some reason it was moved to gtk3... :-/
 >  
 >  -- 
 >  David A. Holland
 >  dholland%netbsd.org@localhost
 >