Subject: Why map package names into buildlink package variable equivalents?
To: None <tech-pkg@netbsd.org>
From: Jeremy C. Reed <reed@reedmedia.net>
List: tech-pkg
Date: 03/31/2004 08:09:20
I received an off-list patch that fixed the inconsistent naming of
variables in builtin.mk and buildlink3.mk in gettext-lib and libiconv
which supposedly (but I never noticed myself) prevent them from being
correctly used by the framework.

Today I noticed that mk/buildlink2/bsd.buildlink2.mk and
mk/buildlink3/bsd.buildlink3.mk have:

# Map package names into buildlink package variable equivalents when it
# differs from the PKGBASE for that package.

What is the purpose of this?

Why don't they use the correct variable names in the first place?

   Jeremy C. Reed
   http://bsd.reedmedia.net/