summaryrefslogtreecommitdiff
path: root/converters/libiconv
AgeCommit message (Collapse)AuthorFilesLines
2005-08-19Put the charset.alias file into place using REQD_FILES instead ofjlam2-4/+4
CONF_FILES since we need it to always be present for libiconv to function properly. It's now no longer removed automatically at deinstallation if it differs from the stock charset.alias file, meaning it's now preserved in case the user made modifications to the file; however a warning will be output that the file can be safely removed if you don't need it anymore. Bump the PKGREVISION to 1.
2005-08-19Merge CONF_FILES/SUPPORT_FILES and CONF_FILES_PERMS/SUPPORT_FILES_PERMSjlam1-2/+2
as the INSTALL and DEINSTALL scripts no longer distinguish between the two types of files. Drop SUPPORT_FILES{,_PERMS} and modify the packages in pkgsrc accordingly.
2005-07-28Changes 1.10:adam7-36/+22
* Added ISO-8859-11 converter. * Updated the ISO-8859-7 converter. * Added ATARIST converter, available through --enable-extra-encodings. * Added BIG5-2003 converter (experimental), available through --enable-extra-encodings. * Updated EUC-TW converter to include the Euro sign. * The preloadable library has been renamed from libiconv_plug.so to preloadable_libiconv.so. * Portability to mingw.
2005-06-06Back out previous and reset the BUILTIN_VERSION.iconv variable instead.jlam1-3/+3
This should fix functioning on Linux systems that actually use GNU libiconv as the builtin iconv implementation.
2005-06-05Make BUILTIN_PKG.iconv follow what the comment says.minskim1-2/+2
2005-06-05Assume that DragonFly's native libiconv is good enough for pkgsrc, just asjmmv1-4/+5
we do for NetBSD. Patch from Joerg Sonnenberger.
2005-06-05In builtin.mk files, use _BLTN_ as the private namespace prefix.jlam1-11/+11
2005-06-01Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.jlam1-62/+85
Several changes are involved since they are all interrelated. These changes affect about 1000 files. The first major change is rewriting bsd.builtin.mk as well as all of the builtin.mk files to follow the new example in bsd.builtin.mk. The loop to include all of the builtin.mk files needed by the package is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk is now included by each of the individual builtin.mk files and provides some common logic for all of the builtin.mk files. Currently, this includes the computation for whether the native or pkgsrc version of the package is preferred. This causes USE_BUILTIN.* to be correctly set when one builtin.mk file includes another. The second major change is teach the builtin.mk files to consider files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most of the builtin.mk files test for the presence of built-in software by checking for the existence of certain files, e.g. <pthread.h>, and we now assume that if that file is under ${LOCALBASE}, then it must be from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The exceptions to this new check are the X11 distribution packages, which are handled specially as noted below. The third major change is providing builtin.mk and version.mk files for each of the X11 distribution packages in pkgsrc. The builtin.mk file can detect whether the native X11 distribution is the same as the one provided by pkgsrc, and the version.mk file computes the version of the X11 distribution package, whether it's built-in or not. The fourth major change is that the buildlink3.mk files for X11 packages that install parts which are part of X11 distribution packages, e.g. Xpm, Xcursor, etc., now use imake to query the X11 distribution for whether the software is already provided by the X11 distribution. This is more accurate than grepping for a symbol name in the imake config files. Using imake required sprinkling various builtin-imake.mk helper files into pkgsrc directories. These files are used as input to imake since imake can't use stdin for that purpose. The fifth major change is in how packages note that they use X11. Instead of setting USE_X11, package Makefiles should now include x11.buildlink3.mk instead. This causes the X11 package buildlink3 and builtin logic to be executed at the correct place for buildlink3.mk and builtin.mk files that previously set USE_X11, and fixes packages that relied on buildlink3.mk files to implicitly note that X11 is needed. Package buildlink3.mk should also include x11.buildlink3.mk when linking against the package libraries requires also linking against the X11 libraries. Where it was obvious, redundant inclusions of x11.buildlink3.mk have been removed.
2005-05-24Don't set artificial restrictions on which platforms can build thisjlam1-7/+1
package. Linux, like NetBSD, should be able to build this package, even if it has a built-in iconv implementation.
2005-05-24Rewrite to use find-libs.mk rename several variables to begin withjlam1-78/+75
_BLNK_ to properly namespace those variables, and rewrite BUILTIN_PKG.iconv computation to use one fewer awk invocation.
2005-05-22Simplify a condition.minskim1-3/+2
2005-05-22Use the iconv library in glibc on Linux even if USE_GNU_ICONV is set.minskim1-2/+3
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/+3
2004-11-24Revision bumpadam1-1/+2
2004-11-24Added a patch for japanese support (PR/25845)adam2-2/+8
2004-11-23Changes 1.9.2:adam5-27/+26
* Bug fixes
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-3/+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-9/+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-08-31Move including the ../../mk/bsd.prefs.mk and checking for Linuxreed1-7/+7
to after GNU_CONFIGURE and USE_LIBTOOL being set. This fixes the problem where the lt_cv_sys_max_cmd_len was not added to the CONFIGURE_ENV. Now that I think about it, I caused this problem when I added that Linux check...
2004-08-28Use the new BUILDLINK_TRANSFORM commands to more precisely state thejlam1-2/+2
intended transformation: use "rm" to remove an option, "rmdir" to remove all options containing a path starting with a given directory name, and "rename" to rename options to something else.
2004-07-04Unused.wiz1-105/+0
2004-06-04Fail if this package is to be built under Linux. This is normalreed1-1/+7
for Linux. Most (all?) Linux distros don't provide a libiconv package, because GLIBC's iconv support is good enough. At this time, using PKG_FAIL_REASON instead of PKG_SKIP_REASON so we can catch examples of packages depending on this. The builtin.mk was improved to help stop it from being used under Linux. This was okayed by Rene Hexel, the maintainer. Todo: fix abiword build because it should not require this libiconv package under Linux.
2004-06-04By default, assume that the native iconv on Linux systems usingreed1-1/+16
GLIBC supports GNU libiconv's API. So don't depend on pkgsrc's libiconv for it. This is normal: most other Linux distros don't provide a libiconv package. This was discussed on tech-pkg list over past two months. It has helped a few users under Linux where they had some problems with conflicts with their working iconv() support provided with libc and the libiconv package. This was okayed by maintainer, Rene Hexel. This still needs some improvement. Some packages still try to force libiconv usage even though not needed.
2004-05-20Revert the change to put -liconv into BUILDLINK_LDFLAGS.iconv (whichdanw1-2/+1
breaks some things on Darwin) and fix audio/musicpd so it doesn't need it (by faking out a configure check that gets confused by the iconv_open -> libiconv_open renaming)
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-05-03Add ${BUILDLINK_LDADD.iconv} to BUILDLINK_LDFLAGS.iconv.snj1-1/+2
2004-04-28nb2: use $(INSTALL), not $(INSTALL_DATA), for a library in an autoconfiscatedtv4-9/+32
package.
2004-04-26Do previous in a different way. We want USE_GNU_ICONV to always usejlam1-19/+73
a GNU libiconv, whether it be builtin or not, and PREFER_{NATIVE,PKGSRC} can be used to decide which iconv we use if USE_GNU_ICONV isn't defined. On NetBSD, the native iconv implementation (if it exists) is considered GNUish enough unless USE_GNU_ICONV is explicitly defined.
2004-04-26If USE_GNU_ICONV is defined, don't use builtin libiconv if ICONV_TYPE issnj1-15/+15
native.
2004-04-02Apparently cp(1) under Irix does not like to overwrite symbolic links.jschauma3-7/+7
This causes the package to fail to install, as this section is executed a second time. Use pax instead and all's peachy.
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-9/+9
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-29Add a BUILDLINK_PKGBASE.<pkg> definition where it's not equal to <pkg>,jlam1-1/+2
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example buildlink[23].mk files in bsd.buildlink[23].mk.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-10Split out the code that deals with checking whether the software isjlam2-104/+85
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-03-02Use ${CP} instead of cp. From Georg Schwarz in PR pkg/24634.snj3-6/+8
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-19/+21
environment overrides all other settings.
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-3/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam2-8/+32
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam2-31/+35
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-11Replace ICONV_IS_GNU with ICONV_TYPE, which can be checked to be eitherjlam2-4/+21
"gnu" or "native".
2004-02-11Move the INCOMPAT_FOO checks to a more natural location within thejlam1-8/+7
block that decides whether package FOO is built-in or not. If the platform is listed in IMCOMPAT_FOO, then treat FOO as being not built-in.
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam1-2/+2
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam2-10/+6
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam2-10/+8
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam2-2/+18
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-2/+2
2004-01-15Don't use "-Wl" on platforms which define "_USE_RPATH" to "no". Thistron1-1/+3
fixes build problems under Darwin.
2004-01-13kill leading whitespace, s/Libiconv/libiconv/grant1-4/+4
2004-01-06Use l:foo: instead of S:...: to remove a library.jlam1-2/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-13 12:58:17 +0000