summaryrefslogtreecommitdiff
path: root/devel/gettext-lib
AgeCommit message (Collapse)AuthorFilesLines
2004-12-18only include <search.h> if it is present. fixes build on Darwin.grant2-1/+17
2004-12-11Create directories before putting files in them. This should fixjlam1-1/+2
PR pkg/28480.
2004-12-03Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs.wiz1-2/+2
Suggested by Roland Illig, ok'd by various.
2004-11-28Remove pre-buildlink and post-buildlink as part of getting pkgsrc readyjlam1-2/+2
for pkgsrc-2004Q4. The "buildlink" phase was removed for the last branch, and this is the final cleanup. "post-buildlink" is now "post-wrapper".
2004-11-27Fix broken libintl existence test; patch by minskim.wiz1-6/+6
2004-11-26Standardize how we search for libraries in builtin.mk files. We definejlam1-9/+14
_BLNK_LIB_FOUND.<lib> to "yes" or "no" depending on whether -l<lib> is found in the base system.
2004-11-21Move the section that sets up some GNU configure variables to forcejlam1-7/+13
"GNU gettext" detection outside of the BROKEN_GETTEXT_DETECTION block. We will need this to happen all the time if we're using a built-in gettext that isn't really GNU gettext.
2004-11-14Follow the recommended template for builtin.mk files: glibc's gettextjlam1-52/+75
is _not_ GNU gettext, so it's presence should not set IS_BUILTIN.gettext to "yes", but it _can_ set USE_BUILTIN.gettext to "yes" to force that it be used. Also, create a new variable BROKEN_GETTEXT_DETECTION, which is yes/no depending on whether or not a package's GNU configure script properly detects -lintl. This variable currently defaults to "yes", but should eventually be set to "no" and overridden on a package-by-package basis for those packages that truly are broken.
2004-10-14If builtin libintl has ngettext(), force packages requiring gettextminskim1-1/+4
API version 2 to choose the builtin library over GNU gettext shipped with each package. In fact, the gettext library included in a package should never be used. Otherwise every such package would install charset.alias and locale.alias, causing conflicts with each other when pkgviews is enabled. For platforms without ngettext() in their builtin libintl (assumed to be gettext-lib-0.10.35nb1 by gettext-lib/builtin.mk), packages requiring gettext API version 2 must add dependency on gettext-lib>=0.10.36 to share devel/gettext-lib rather than to link statically against the included gettext library.
2004-10-04older versions of GNU gettext do not provide ngettext() and a bunchgrant1-5/+15
of other functions. only consider the base system's gettext suitable if it provides at least ngettext().
2004-10-03Correct typo "PREFER.getext".heinz1-2/+2
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-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-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-186/+0
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-09Pass -b to pkg_admin lsbest to make this work correctly on systems where the ↵danw1-2/+2
pkgdbdir passes through a symlink
2004-04-20Use $(INSTALL), not $(INSTALL_DATA), to install a library. Some platformstv3-7/+16
(e.g., Interix) still expect a shlib to be executable, and INSTALL_DATA installs with mode 644 (non-executable).
2004-04-06Do not assume that if /usr/lib/libintl.* does not existreed1-3/+14
that it can not be builtin. So also check for "This file is part of the GNU C Library". This helps with systems that have gettext(3) functionality included in their glibc. This also fixes build problem under Linux where devel/popt didn't build "because some functions are defined both in gettext-lib and in the native libc" as reported by minskim to tech-pkg on 21/Mar/2004.
2004-04-01Add a script to workaround uses of msgid_plural, which is not yet supportedjmmv2-2/+38
by our native libintl. While it is not implemented, this allows us to build programs against the native libintl, loosing very few functionality (some translations of plural messages on few languages), and avoiding runtime conflicts between native libintl and the gnu one (coming from the gettext package). Packages including .po files with uses of msgid_plural should define the USE_MSGFMT_PLURALS variable to 'yes', so that the msgfmt wrapper is used. (Do not use it when not really needed, as it will pull in perl5 as a build dependancy).
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-9/+13
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-22Assume that the native gettext implementation will satisfy GNU gettextjlam1-7/+8
dependencies unless USE_GNU_GETTEXT is defined or IMCOMPAT_GETTEXT is set appropriately. This should allow packages to use the glibc gettext routines on Linux.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-3/+2
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
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-16Manipulate the buildlink depth so that libiconv and Xfixes aren't addedjlam1-1/+3
to BUILDLINK_DEPENDS unless their respective buildlink3.mk files are included by the top-level Makefile.
2004-03-10Split out the code that deals with checking whether the software isjlam2-146/+155
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-08Improvements for DESCRiption and COMMENT.reed2-4/+5
(The DESCRiption was same as the other gettext package, and the COMMENT mentioned "Tools".)
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-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-14USE_BUILDLINK should be "yes", not just defined.jlam1-4/+4
2004-02-14remove unneeded CONFIG_{GUESS,SUB}_OVERRIDE, as bsd.pkg.mk does thisgrant1-3/+1
automatically now.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam2-6/+26
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-51/+57
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-11Move the INCOMPAT_FOO checks to a more natural location within thejlam1-14/+14
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-3/+3
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-7/+16
2004-01-15Don't use "-Wl" on platforms which define "_USE_RPATH" to "no". Thistron1-1/+3
fixes build problems under Darwin.
2004-01-11Add some double quotes and move a section into a protected region so wejlam1-15/+14
don't keep re-evaluating it.
2004-01-06Use l:foo: instead of S:...: to remove a library.jlam1-2/+2
2004-01-06It's "overwrite" not "overview"!!jlam1-2/+2
2004-01-05bl3ifyjlam1-3/+5
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-05Don't need to set BUILDLINK_PREFIX.gettext explicitly as bsd.buildlink3.mkjlam1-2/+1
does it correctly for us.
2004-01-05Sow BUILDLINK_USE_BUILTIN.<pkg> and reap _NEED_<PKG> variables.jlam1-16/+21
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-4/+4
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+129
buildlink3 framework.
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-30 16:52:14 +0000