summaryrefslogtreecommitdiff
path: root/converters/fribidi
AgeCommit message (Collapse)AuthorFilesLines
2006-03-11Convert all packages using REPLACE_INTERPRETER to the new variable namesghen1-4/+4
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.
2006-03-09Use REPLACE_INTERPRETER instead of a patch.ghen3-13/+7
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
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.
2005-08-10Remove the abuse of buildlink that was pkg-config/buildlink3.mk. Thatjlam1-2/+2
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.
2005-07-21Change path from devel/pkgconfig to devel/pkg-config.wiz1-2/+2
No PKGREVISION bump since pkg-config is only a BUILD_DEPENDS.
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-23Add RMD160 digests in addition to SHA1 onesagc1-1/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-2/+4
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.
2004-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-5/+1
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".
2004-05-07Drop maintainership; I don't have the enough free time to maintainxtraeme1-2/+2
all these packages.
2004-04-25Unused.wiz1-24/+0
2004-04-15The buildlink2 framework does nothing with .pc files -- remove themwiz1-2/+1
from the buildlink2.mk files.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-11/+7
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-15Convert to buildlink3.wiz2-3/+25
2004-02-14PKGCONFIG_OVERRIDE is relative to WRKSRC.jmmv1-2/+2
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2003-12-30Whitespace fixcjep1-2/+1
2003-12-14Initial import of fribidi-0.10.4 from pkgsrc-wip.xtraeme6-0/+105
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.