Problems found with existing distfile:
distfiles/libiconv-1.13-cp932.patch.gz
No changes made to the libiconv distinfo file.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Overview of changes between 0.19.6 and 0.19.7
=============================================
* Disable thread-unsafe memory pool by default. (bug #79385)
* Misc fixes.
This commit restores the ABI_DEPENDS line that was there until
yesterday, 0.10.4nb1. It's unclear what the right answer is for
fribidi and ABI_DEPENDS, and if revbumping is needed - so for now
avoid the issue.
Based on a report from Bob Bernstein, m17n-lib does not build with
0.10.9. According to
http://upstream-tracker.org/versions/fribidi.html
there was an API and ABI break at 0.19.1, and then it has been
essentially stable.
Overview of changes between 0.19.5 and 0.19.6
=============================================
* Fix two minor bidi bugs.
* Build with new libtool to support ppc64le.
-- Adjust path in patches for above change
(patch target moved, and unfortunately, patches name
now reflecting target path, so renamed them).
-- Correct target path in Makefile.
-- m17n-{db,lib} 1.6.4 ask for this version.
Overview of changes between 0.19.4 and 0.19.5
=============================================
* Update to Unicode 6.2.0.
Overview of changes between 0.19.2 and 0.19.4
=============================================
* Update to Unicode 6.1.0.
* Misc fixes.
Overview of changes between 0.19.1 and 0.19.2
=============================================
* Update to Unicode Character Database 5.1.0
* Fixed bug in Arabic ligature table (bug #208870)
* Handle RLM/LRM in CP1255 charset converter. (bug #15328, Artyom)
Overview of changes between 0.10.9 and 0.19.1
=============================================
* This is the first release of the fribidi2 module in CVS, mostly
developed in 2004 and 2005.
* Support for Arabic joining/shaping added.
* API for correct handling of multi-line paragraphs added.
* Restructured code base.
* Supposed to be fully API/ABI compatible with 0.10 releases.
Please report if it is not.
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
Changes since 0.10.4:
* Minor bugfix.
* Update to Unicode Character Database 5.0.0
* Fixed type sizes when stdint.h is not available.
* Fixed type sizes on 64-bit architectures.
* We have moved to http://fribidi.org/, hosted on freedesktop.org.
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).
without underscores (REPLACE.*.old, REPLACE.*.new, and REPLACE_FILES.*).
Also convert REPLACE.*.new= ${SH:Q} back to ${SH}, as it should not be quoted
here, if at all.
Ok with rillig.
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.
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".
Free Implementation of the Unicode Bidirectional Algorithm.
The library implements all of the algorithm as described in the "Unicode
Standard Annex #9, The Bidirectional Algorithm,
http://www.unicode.org/unicode/reports/tr9/". FriBidi is exhautively tested
against Bidi Reference Code, and due to our best knowledge, does not contain
any conformance bugs.
In the API, we were inspired by the document "Bi-Di languages support - BiDi
API proposal" by Franck Portaneri which he wrote as a proposal for adding BiDi
support to Mozilla.
Internally the library uses Unicode entirely. The character property function
was automatically created from the Unicode property list data file,
PropList.txt, available from the Unicode Online Data site. This means that
every Unicode character will be treated in strict accordance with the Unicode
specification. The same is true for the mirroring of characters, which also
works for all the characters listed as mirrorable in the Unicode specification.
