and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
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).
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.
(SILC) protocol Toolkit.
SILC (Secure Internet Live Conferencing) is a protocol which provides
secure conferencing services in the Internet over insecure channel.
SILC superficially resembles IRC, although they are very different
internally. SILC is much more than just about `encrypting the traffic'.
That is easy enough to do with IRC and SSL hybrids, but even then the
entire network cannot be secured, only part of it.
SILC provides security services, such as sending private messages entirely
secure; noone can see the message except you and the real receiver of the
message. SILC also provides same functionality for channels; noone except
those clients joined to the channel may see the messages destined to the
channel. Communication between client and server is also secured with
session keys and all commands, authentication data (such as passwords etc.)
and other traffic is entirely secured. The entire network, and all parts of
it, is secured.
SILC has secure key exchange protocol that is used to create the session keys
for each connection. SILC also provides strong authentication based on either
passwords or public key authentication. All authentication data is always
encrypted in the SILC network. Each connection has their own session keys,
all channels have channel specific keys, and all private messages can be
secured with private message specific keys.
