summaryrefslogtreecommitdiff
path: root/fonts/fontconfig/buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2006-07-08Change the format of BUILDLINK_ORDER to contain depth information as well,jlam1-2/+2
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
2006-07-08Track information in a new variable BUILDLINK_ORDER that informs usjlam1-1/+2
of the order in which buildlink3.mk files are (recursively) included by a package Makefile.
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
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).
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg1-2/+2
2006-01-24Bump BUILDLINK_RECOMMENDED of textproc/expat to 2.0.0 becausewiz1-2/+2
of the shlib major bump. PKGREVISION++ for the dependencies.
2005-04-21Include converters/libiconv/buildlink3.mk.kristerw1-1/+2
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-1/+2
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-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-10Split out the code that deals with checking whether the software isjlam1-109/+11
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-02-19Add BUILDLINK_DEPENDS.<pkg> for dependencies in a section that is invokedjlam1-5/+3
only if we're not using the built-in versions of the package.
2004-02-19Move the settings, which force the use of builtin versions of dependenciesjlam1-5/+8
if the builtin version of the package is being used, into a global location so that they're always executed.
2004-02-18If we're using the built-in version of the software, then we must alsojlam1-4/+8
be using built-in versions of any other software pulled in via buildlink3.mk files.
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-16/+18
environment overrides all other settings.
2004-02-18fontconfig had a really weird version numbering system. Version 2.0 isjlam1-2/+2
practically verbatim with the "1.0.1" release that's in XFree86 4.3.x. There have in fact been only function additions to the fontconfig API since 2.0, so fontconfig has never actually had a bump in the shared library major. Therefore, allow "fontconfig>=1.0.1" as the base requirement.
2004-02-17When using the native version of this library, symlink the .pc file intojmmv1-1/+2
the buildlink directory so that pkg-config can find it. Ok'ed by jlam@.
2004-02-17Missing a "=" in the ">=".jlam1-2/+2
2004-02-17Don't include other buildlink3.mk files if we're just checking whether thejlam1-4/+6
software is built-in.
2004-02-16fontconfig is in the "fonts" category.jlam1-2/+2
2004-02-16Typo.jlam1-2/+2
2004-02-16Do the dance to check the version of the XFree86-provided fontconfig.jlam1-8/+97
Also correct the list of buildlink2.mk files included by fontconfig/buildlink2.mk.
2004-02-09Raise BUILDLINK_DEPENDS.freetype2 to at least 2.1.3.reed1-2/+2
Even 2.0.9 is not good enough for newer fontconfig; for example, gtk2 won't buildlink correctly (and will use older X version of include/freetype2/freetype/ftbdf.h) and libfontconfig needs FT_Get_BDF_Property which is not defined. No PKGREVISION bump is needed, because would not even build in first place.
2004-01-24Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. Injlam1-2/+2
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
2004-01-24bl3ifyjlam1-0/+22
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-30 12:12:29 +0000