a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
* bug fixes
* new features
* compatibility breakers:
SMPP module users should note that the 'msg-id-type' default behaviour
has changed. The SMPP spec says that msg ids should be C strings and
hence we treat them as such per default. If your SMSC gives msg ids
in submit_sm and deliver_dm PDUs in different numbering basing, then
please use the 'msg-id-type' config directive to set it accordingly.
- removing CFLAGS+=_I${LOCALBASE}/include and CPPFLAGS+= -I${LOCALBASE}/include
- removing libxml and pth from DEPENDS and including theirs buildlink.mk files
We should all thank Johnny C. Lam for this buildlink.mk stuff -- it makes
life simplier.
