RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
changes:
* remove #ifdef OSIP_RETRANSMIT_2XX to always compile it.
* initialize remote_contact_uri when dialog is built with notify.
* allow very short attachements.
* new macros allocators.
* remove use of alloca in the parser.
* fix memory bug when realloc is needed on large message.
* remove useless prototypes.
* fix memory access in parser.
* API slightly broken to enable support for binary data.
* improvements of the sip message test suite.
The binary compatibility and API compatibility has been lost
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.
oSIP is an implementation of SIP.
The GNU oSIP library is written in C and get no dependencies except the
standard C library. oSIP is thread safe and will generally be used in a
multi-threaded application. Nevertheless, this is optional.
oSIP is little in size and code and thus could be use to implement IP
soft-phone as well as embedded SIP software. oSIP is not limited to
endpoint agents, and can also be used to implement "SIP proxy".
oSIP does not intend to provide a high layer API for controlling
"SIP Session" at this step. Instead, it currently provides an API for the
SIP message parser, SDP message parser, and library to handle
"SIP transactions" as defined by the SIP document.
