[pkgsrc/trunk]: pkgsrc/textproc/enchant2 Make enchant2 bl3 create enchant.pc.

[bsiegert <bsiegert%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/81255fe7fc74
branches:  trunk
changeset: 315222:81255fe7fc74
user:      bsiegert <bsiegert%pkgsrc.org@localhost>
date:      Sun Nov 18 13:08:19 2018 +0000

description:
Make enchant2 bl3 create enchant.pc.

I have enough of these manual hacks in configure scripts that check for
'enchant => someversion' instead of 'enchant-2 >= someversion'. Instead,
let's give them the former.

Caveat: this makes it impossible to have enchant and enchant-2 buildlinked
into the same build, but you do not want that.

diffstat:

 textproc/enchant2/buildlink3.mk |  9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diffs (23 lines):

diff -r e56b73eaeabb -r 81255fe7fc74 textproc/enchant2/buildlink3.mk
--- a/textproc/enchant2/buildlink3.mk   Sun Nov 18 12:06:23 2018 +0000
+++ b/textproc/enchant2/buildlink3.mk   Sun Nov 18 13:08:19 2018 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: buildlink3.mk,v 1.1 2018/11/01 09:36:47 bsiegert Exp $
+# $NetBSD: buildlink3.mk,v 1.2 2018/11/18 13:08:19 bsiegert Exp $
 
 BUILDLINK_TREE+=       enchant2
 
@@ -9,6 +9,13 @@
 BUILDLINK_ABI_DEPENDS.enchant2+=       enchant2>=2.2.3
 BUILDLINK_PKGSRCDIR.enchant2?= ../../textproc/enchant2
 
+# Lots of older software looks for enchant.pc instead of enchant-2.pc.
+${BUILDLINK_DIR}/lib/pkgconfig/enchant.pc:
+       ${MKDIR} ${BUILDLINK_DIR}/lib/pkgconfig
+       cd ${BUILDLINK_DIR}/lib/pkgconfig && ${LN} -sf enchant-2.pc enchant.pc
+
+buildlink-enchant2-cookie: ${BUILDLINK_DIR}/lib/pkgconfig/enchant.pc
+
 # spelling libraries are loaded dynamically and do not need
 # to be included here
 .include "../../devel/glib2/buildlink3.mk"