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).
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.
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
New in 0.0.15:
** Documentation improvements.
For example, you can now browse the GSS manual using DevHelp.
** Libtool's -export-symbols-regex is now used to only export official APIs.
Before, applications might accidentally access internal functions.
Note that this is not supported on all platforms, so you must still
make sure you are not using undocumented symbols in GSS.
* Version 0.0.14 (released 2004-10-15)
** gss_import_name and gss_duplicate_name no longer clone the OID.
Instead, only the pointer to the OID is cloned. It seem unclear where
a cloned OID would be deallocated.
** Fixed handling of sequence numbers in gss_accept_sec_context, for servers.
** Fix crash in gss_accept_sec_context for NULL values of ret_flags.
** Fix memory leaks.
** Sync with new Shishi 0.0.18 API.
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.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
* Changes in 0.0.13 (released 2004-08-08)
** Revamp of gnulib compatibility files.
** More translations.
French (by Michel Robitaille) and Romanian (by Laurentiu Buzdugan).
* Changes in 0.0.12 (released 2004-08-01)
** Added rudimentary self tests of Kerberos 5 context init/accept.
Tests client and server authentication, with and without mutual
authentication, and that various aspects of the API like ret_flags
work.
** Various fixes, discovered while writing the Kerberos 5 self test.
** Cross compile builds should work.
It should work for any sane cross compile target, but the only tested
platform is uClibc/uClinux on Motorola Coldfire.
* Changes in 0.0.11 (released 2004-04-18)
** Minor cleanups to the core header file.
Using xom.h is no longer supported (the file doesn't exist on modern
systems).
** Kerberos 5 sequence number handling fixed.
First, gss_init_sec_context set the sequence numbers correctly, before
the incorrect sequence numbers prevented gss_(un)wrap from working
correctly. Secondly, gss_unwrap now check the sequence numbers
correctly. This was prompted by the addition of randomized sequence
numbers by default in Shishi 0.0.15.
** The compatibility files in gl/ where synced with Gnulib.
** Various bugfixes and cleanups.
** Polish translation added, by Jakub Bogusz.
Changes since 0.0.6:
- A command line tool "gss" added in src/.
- gss_display_status can return multiple description texts (using context).
- The Swedish translation has been updated.
- Various cleanups and improvements.
- Implemented gss_export_name and gss_krb5_inquire_cred_by_mech.
The Kerberos 5 backend also support them.
- gss_inquire_cred support default credentials.
- Kerberos 5 gss_canonicalize_name now support all mandatory name types.
- Kerberos 5 gss_accept_sec_context now support sub-session keys in AP-REQ.
- Added new extended function API: gss_userok.
- API documentation in HTML format from GTK-DOC included in doc/reference/.
- Moved all backend specific code into sub-directories of lib/.
- The gss_duplicate_name function now allocate the output result properly.
- Man pages for all public functions are included.
- Documentation fixes. For example, all official APIs are now documented.
- Fixed typo that broke gss_wrap for 3DES with Kerberos 5.
- Improvements to build environment.
- Autoconf 2.59, Automake 1.8 beta, Libtool CVS used.
GSS is an implementation of the Generic Security Service Application Program
Interface (GSS-API). GSS-API is used by network servers (e.g., IMAP, SMTP) to
provide security security services, e.g., authenticate clients against servers.
GSS consists of a library and a manual.
