From owner-p4-projects@FreeBSD.ORG Tue Dec 27 13:52:00 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 64C751065673; Tue, 27 Dec 2011 13:52:00 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26C9E106566C for ; Tue, 27 Dec 2011 13:52:00 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id 128088FC13 for ; Tue, 27 Dec 2011 13:52:00 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id pBRDpxPl032978 for ; Tue, 27 Dec 2011 13:51:59 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id pBRDpxLh032975 for perforce@freebsd.org; Tue, 27 Dec 2011 13:51:59 GMT (envelope-from rene@FreeBSD.org) Date: Tue, 27 Dec 2011 13:51:59 GMT Message-Id: <201112271351.pBRDpxLh032975@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 203591 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 13:52:00 -0000 http://p4web.freebsd.org/@@203591?ac=10 Change 203591 by rene@rene_acer on 2011/12/27 13:51:41 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#117 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/freebsd-update-server/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#43 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#120 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.sgml#51 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.sgml#48 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/share/sgml/mailing-lists.ent#42 integrate .. //depot/projects/docproj_nl/share/sgml/man-refs.ent#36 integrate .. //depot/projects/docproj_nl/www/en/java/news.xml#11 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#117 (text+ko) ==== @@ -1,4 +1,4 @@ - + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#43 (text+ko) ==== @@ -11,7 +11,7 @@ The &os; Ports Management Team - $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.83 2011/12/12 01:54:41 linimon Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.84 2011/12/24 21:22:29 linimon Exp $ 2003 @@ -2477,6 +2477,21 @@ This section is in progress. + + Configuring <literal>src</literal> + + + + + Add the following to etc/sysctl.conf: +kern.maxfiles=40000 + + + + + + + Configuring <literal>ports</literal> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#120 (text+ko) ==== @@ -1,7 +1,7 @@ The minimal Makefile would look something like this: - # New ports collection makefile for: oneko + # New ports collection makefile for: oneko # Date created: 5 December 1994 # Whom: asami # # $FreeBSD$ # -PORTNAME= oneko -PORTVERSION= 1.1b -CATEGORIES= games -MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/ +PORTNAME= oneko +PORTVERSION= 1.1b +CATEGORIES= games +MASTER_SITES= ftp://ftp.cs.columbia.edu/archives/X11R5/contrib/ -MAINTAINER= asami@FreeBSD.org -COMMENT= A cat chasing a mouse all over the screen +MAINTAINER= asami@FreeBSD.org +COMMENT= A cat chasing a mouse all over the screen -MAN1= oneko.1 -MANCOMPRESSED= yes -USE_IMAKE= yes +MAN1= oneko.1 +MANCOMPRESSED= yes +USE_IMAKE= yes .include <bsd.port.mk> @@ -238,12 +238,12 @@ oneko port by adding the following lines to the Makefile: - PLIST_FILES= bin/oneko \ - lib/X11/app-defaults/Oneko \ - lib/X11/oneko/cat1.xpm \ - lib/X11/oneko/cat2.xpm \ - lib/X11/oneko/mouse.xpm -PLIST_DIRS= lib/X11/oneko + PLIST_FILES= bin/oneko \ + lib/X11/app-defaults/Oneko \ + lib/X11/oneko/cat1.xpm \ + lib/X11/oneko/cat2.xpm \ + lib/X11/oneko/mouse.xpm +PLIST_DIRS= lib/X11/oneko Of course, PLIST_DIRS should be left unset if a port installs no directories of its own. @@ -738,7 +738,7 @@ Makefile. A list of files to convert can be specified: - USE_DOS2UNIX= util.c util.h + USE_DOS2UNIX= util.c util.h If you want to convert a group of files across subdirectories, DOS2UNIX_REGEX can be used. Its argument is @@ -747,8 +747,8 @@ converting all files of a given extension, for example all source code files leaving binary files intact: - USE_DOS2UNIX= yes -DOS2UNIX_REGEX= .*\.(c|cpp|h) + USE_DOS2UNIX= yes +DOS2UNIX_REGEX= .*\.(c|cpp|h) If you want to create a patch file based off of an existing file, you can copy it with an @@ -1010,8 +1010,8 @@ 0.10, is committed to the ports collection: - PORTNAME= gtkmumble -PORTVERSION= 0.10 + PORTNAME= gtkmumble +PORTVERSION= 0.10 PKGNAME becomes gtkmumble-0.10. @@ -1020,9 +1020,9 @@ FreeBSD patch. PORTREVISION is bumped accordingly. - PORTNAME= gtkmumble -PORTVERSION= 0.10 -PORTREVISION= 1 + PORTNAME= gtkmumble +PORTVERSION= 0.10 +PORTREVISION= 1 PKGNAME becomes gtkmumble-0.10_1 @@ -1040,9 +1040,9 @@ PORTREVISION is reset to 0 (or removed from the Makefile). - PORTNAME= gtkmumble -PORTVERSION= 0.2 -PORTEPOCH= 1 + PORTNAME= gtkmumble +PORTVERSION= 0.2 +PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.2,1 @@ -1051,9 +1051,9 @@ PORTEPOCH never decreases, the version variables are now: - PORTNAME= gtkmumble -PORTVERSION= 0.3 -PORTEPOCH= 1 + PORTNAME= gtkmumble +PORTVERSION= 0.3 +PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.3,1 @@ -2325,8 +2325,8 @@ MASTER_SITE_SUBDIR to the path within the archive. Here is an example: - MASTER_SITES= ${MASTER_SITE_GNU} -MASTER_SITE_SUBDIR= make + MASTER_SITES= ${MASTER_SITE_GNU} +MASTER_SITE_SUBDIR= make Or you can use a condensed format: @@ -2454,8 +2454,8 @@ foo.tgz instead of the more normal foo.tar.gz, you would write: - DISTNAME= foo -EXTRACT_SUFX= .tgz + DISTNAME= foo +EXTRACT_SUFX= .tgz The USE_BZIP2 and USE_ZIP variables automatically set EXTRACT_SUFX to @@ -2482,7 +2482,7 @@ space separated list of all the files that must be downloaded. - DISTFILES= source1.tar.gz source2.tar.gz + DISTFILES= source1.tar.gz source2.tar.gz If not explicitly set, DISTFILES defaults to ${DISTNAME}${EXTRACT_SUFX}. @@ -2496,8 +2496,8 @@ another is an uncompressed document—list the filenames that must be extracted in EXTRACT_ONLY. - DISTFILES= source.tar.gz manual.html -EXTRACT_ONLY= source.tar.gz + DISTFILES= source.tar.gz manual.html +EXTRACT_ONLY= source.tar.gz If none of the DISTFILES should be uncompressed then set EXTRACT_ONLY to @@ -2572,7 +2572,7 @@ [0-9] and denote a group designation. For example: - DISTFILES= alpha:0 beta:1 + DISTFILES= alpha:0 beta:1 In OpenBSD, distribution file alpha will be associated with variable @@ -2645,9 +2645,9 @@ Simplified use of <literal>MASTER_SITES:n</literal> with 1 file per site - MASTER_SITES= ftp://ftp.example1.com/:source1 \ + MASTER_SITES= ftp://ftp.example1.com/:source1 \ ftp://ftp.example2.com/:source2 -DISTFILES= source1.tar.gz:source1 \ +DISTFILES= source1.tar.gz:source1 \ source2.tar.gz:source2 @@ -2665,9 +2665,9 @@ Simplified use of <literal>MASTER_SITES:n</literal> with more than 1 file per site - MASTER_SITES= ftp://ftp.example1.com/:source1 \ + MASTER_SITES= ftp://ftp.example1.com/:source1 \ ftp://ftp.example2.com/:source2 -DISTFILES= source1.tar.gz:source1 \ +DISTFILES= source1.tar.gz:source1 \ source2.tar.gz:source2 \ source3.tar.gz:source2 @@ -2728,9 +2728,9 @@ The following examples are equivalent but the first one is preferred: - MASTER_SITES= alpha + MASTER_SITES= alpha -MASTER_SITES= alpha:DEFAULT + MASTER_SITES= alpha:DEFAULT @@ -2756,13 +2756,13 @@ All the following examples are equivalent but the last one is preferred: - MASTER_SITES= alpha alpha:SOME_SITE + MASTER_SITES= alpha alpha:SOME_SITE -MASTER_SITES= alpha:DEFAULT alpha:SOME_SITE + MASTER_SITES= alpha:DEFAULT alpha:SOME_SITE -MASTER_SITES= alpha:SOME_SITE,DEFAULT + MASTER_SITES= alpha:SOME_SITE,DEFAULT -MASTER_SITES= alpha:DEFAULT,SOME_SITE + MASTER_SITES= alpha:DEFAULT,SOME_SITE @@ -2821,7 +2821,7 @@ MASTER_SITES:n in MASTER_SITE_SUBDIR - MASTER_SITE_SUBDIR= old:n new/:NEW + MASTER_SITE_SUBDIR= old:n new/:NEW @@ -2843,16 +2843,16 @@ operator, multiple files, multiple sites and multiple subdirectories - MASTER_SITES= http://site1/%SUBDIR%/ http://site2/:DEFAULT \ + MASTER_SITES= http://site1/%SUBDIR%/ http://site2/:DEFAULT \ http://site3/:group3 http://site4/:group4 \ http://site5/:group5 http://site6/:group6 \ http://site7/:DEFAULT,group6 \ http://site8/%SUBDIR%/:group6,group7 \ http://site9/:group8 -DISTFILES= file1 file2:DEFAULT file3:group3 \ +DISTFILES= file1 file2:DEFAULT file3:group3 \ file4:group4,group5,group6 file5:grouping \ file6:group7 -MASTER_SITE_SUBDIR= directory-trial:1 directory-n/:groupn \ +MASTER_SITE_SUBDIR= directory-trial:1 directory-n/:groupn \ directory-one/:group6,DEFAULT \ directory @@ -3041,8 +3041,8 @@ MASTER_SITES:n with MASTER_SITE_SOURCEFORGE - MASTER_SITES= http://site1/ ${MASTER_SITE_SOURCEFORGE:S/$/:sourceforge,TEST/} -DISTFILES= something.tar.gz:sourceforge + MASTER_SITES= http://site1/ ${MASTER_SITE_SOURCEFORGE:S/$/:sourceforge,TEST/} +DISTFILES= something.tar.gz:sourceforge something.tar.gz will be @@ -3066,8 +3066,8 @@ MASTER_SITES:n with PATCH_SITES. - PATCH_SITES= http://site1/ http://site2/:test -PATCHFILES= patch1:test + PATCH_SITES= http://site1/ http://site2/:test +PATCHFILES= patch1:test @@ -3240,8 +3240,8 @@ id="ports-master-sites-n-example-always-keep-distfiles"> Use of <makevar>ALWAYS_KEEP_DISTFILES</makevar>. .if defined(PACKAGE_BUILDING) -DISTFILES+= foo.tar.gz -ALWAYS_KEEP_DISTFILES= yes +DISTFILES+= foo.tar.gz +ALWAYS_KEEP_DISTFILES= yes .endif @@ -3309,7 +3309,7 @@ should begin with a capital and end without a period. Here is an example: - COMMENT= A cat chasing a mouse all over the screen + COMMENT= A cat chasing a mouse all over the screen The COMMENT variable should immediately follow the MAINTAINER variable in the Makefile. @@ -3342,9 +3342,11 @@ shared library, dir is the directory in which to find it in case it is not available, and target is the target to call in that - directory. For example, - LIB_DEPENDS= jpeg.9:${PORTSDIR}/graphics/jpeg - will check for a shared jpeg library with major version 9, and + directory. For example, + + LIB_DEPENDS= jpeg.9:${PORTSDIR}/graphics/jpeg + + will check for a shared jpeg library with major version 9, and descend into the graphics/jpeg subdirectory of your ports tree to build and install it if it is not found. The target part can be omitted if it is @@ -3390,8 +3392,8 @@ For example, - RUN_DEPENDS= ${LOCALBASE}/etc/innd:${PORTSDIR}/news/inn \ - xmlcatmgr:${PORTSDIR}/textproc/xmlcatmgr + RUN_DEPENDS= ${LOCALBASE}/etc/innd:${PORTSDIR}/news/inn \ + xmlcatmgr:${PORTSDIR}/textproc/xmlcatmgr will check if the file or directory /usr/local/etc/innd exists, and build and @@ -3432,7 +3434,7 @@ case, it is both tempting and intuitive to directly assign one to the other: - RUN_DEPENDS= ${BUILD_DEPENDS} + RUN_DEPENDS= ${BUILD_DEPENDS} However, such assignment can pollute run-time dependencies with entries not defined in the port's original BUILD_DEPENDS. @@ -3447,7 +3449,7 @@ with expansion, i.e. expand the value before assigning it to the variable: - RUN_DEPENDS:= ${BUILD_DEPENDS} + RUN_DEPENDS:= ${BUILD_DEPENDS} @@ -3457,8 +3459,11 @@ requires to build. Like RUN_DEPENDS, it is a list of path:dir:target - tuples. For example, BUILD_DEPENDS= - unzip:${PORTSDIR}/archivers/unzip will check + tuples. For example, + + BUILD_DEPENDS= unzip:${PORTSDIR}/archivers/unzip + + will check for an executable called unzip, and descend into the archivers/unzip subdirectory of your ports tree to build and install it if it is not found. @@ -3478,8 +3483,11 @@ This variable specifies executables or files this port requires to fetch. Like the previous two, it is a list of path:dir:target - tuples. For example, FETCH_DEPENDS= - ncftp2:${PORTSDIR}/net/ncftp2 will check for an + tuples. For example, + + FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2 + + will check for an executable called ncftp2, and descend into the net/ncftp2 subdirectory of your ports tree to build and install it if it is not found. @@ -3496,8 +3504,11 @@ This variable specifies executables or files this port requires for extraction. Like the previous, it is a list of path:dir:target - tuples. For example, EXTRACT_DEPENDS= - unzip:${PORTSDIR}/archivers/unzip will check + tuples. For example, + + EXTRACT_DEPENDS= unzip:${PORTSDIR}/archivers/unzip + + will check for an executable called unzip, and descend into the archivers/unzip subdirectory of your ports tree to build and install it if it is not found. @@ -3522,9 +3533,11 @@ This variable specifies executables or files this port requires to patch. Like the previous, it is a list of path:dir:target - tuples. For example, PATCH_DEPENDS= - ${NONEXISTENT}:${PORTSDIR}/java/jfc:extract - will descend into the + tuples. For example, + + PATCH_DEPENDS= ${NONEXISTENT}:${PORTSDIR}/java/jfc:extract + + will descend into the java/jfc subdirectory of your ports tree to extract it. @@ -3554,8 +3567,11 @@ It is always incorrect to set any USE_* in /etc/make.conf. For instance, - setting USE_GCC=3.4 - would add a dependency on gcc34 for every port, + setting + + USE_GCC= 3.4 + + would add a dependency on gcc34 for every port, including gcc34 itself! @@ -3688,11 +3704,11 @@ RUN_DEPENDS. Use this only when you need to get the source of the other port. You can often save compilation time by specifying the target too. For - instance + instance - BUILD_DEPENDS= ${NONEXISTENT}:${PORTSDIR}/graphics/jpeg:extract + BUILD_DEPENDS= ${NONEXISTENT}:${PORTSDIR}/graphics/jpeg:extract - will always descend to the jpeg port and extract it. + will always descend to the jpeg port and extract it. @@ -3735,18 +3751,18 @@ This will be best demonstrated by an example. This is part of japanese/xdvi300/Makefile; - PORTNAME= xdvi -PORTVERSION= 17 -PKGNAMEPREFIX= ja- -PKGNAMESUFFIX= ${RESOLUTION} + PORTNAME= xdvi +PORTVERSION= 17 +PKGNAMEPREFIX= ja- +PKGNAMESUFFIX= ${RESOLUTION} : # default -RESOLUTION?= 300 +RESOLUTION?= 300 .if ${RESOLUTION} != 118 && ${RESOLUTION} != 240 && \ - ${RESOLUTION} != 300 && ${RESOLUTION} != 400 - @${ECHO_MSG} "Error: invalid value for RESOLUTION: \"${RESOLUTION}\"" - @${ECHO_MSG} "Possible values are: 118, 240, 300 (default) and 400." - @${FALSE} + ${RESOLUTION} != 300 && ${RESOLUTION} != 400 + @${ECHO_MSG} "Error: invalid value for RESOLUTION: \"${RESOLUTION}\"" + @${ECHO_MSG} "Possible values are: 118, 240, 300 (default) and 400." + @${FALSE} .endif japanese/xdvi300 also has all the regular @@ -3757,8 +3773,8 @@ As for other resolutions, this is the entire xdvi118/Makefile: - RESOLUTION= 118 -MASTERDIR= ${.CURDIR}/../xdvi300 + RESOLUTION= 118 +MASTERDIR= ${.CURDIR}/../xdvi300 .include "${MASTERDIR}/Makefile" @@ -3826,13 +3842,13 @@ Here is an example that puts it all together. - MAN1= foo.1 -MAN3= bar.3 -MAN4= baz.4 -MLINKS= foo.1 alt-name.8 -MANLANG= "" ja -MAN3PREFIX= ${PREFIX}/share/foobar -MANCOMPRESSED= yes + MAN1= foo.1 +MAN3= bar.3 +MAN4= baz.4 +MLINKS= foo.1 alt-name.8 +MANLANG= "" ja +MAN3PREFIX= ${PREFIX}/share/foobar +MANCOMPRESSED= yes This states that six files are installed by this port; @@ -3851,10 +3867,10 @@ If only some manpages are translated, you can use several variables dynamically created from MANLANG content: - MANLANG= "" de ja -MAN1= foo.1 -MAN1_EN= bar.1 -MAN3_DE= baz.3 + MANLANG= "" de ja +MAN1= foo.1 +MAN1_EN= bar.1 +MAN3_DE= baz.3 This translates into this list of files: @@ -3880,10 +3896,11 @@ For example, lang/gcc34 installs info files to PREFIX/INFO_PATH/gcc34, - and INFO will be something like this: - INFO= gcc34/cpp gcc34/cppinternals gcc34/g77 ... - - Appropriate installation/de-installation code will be automatically + and INFO will be something like this: + + INFO= gcc34/cpp gcc34/cppinternals gcc34/g77 ... + + Appropriate installation/de-installation code will be automatically added to the temporary pkg-plist before package registration. @@ -4038,12 +4055,11 @@ Syntax - The syntax for the OPTIONS variable is: + The syntax for the OPTIONS variable is: -OPTIONS= OPTION "descriptive text" default ... - + OPTIONS= OPTION "descriptive text" default ... - The value for default is either ON or + The value for default is either ON or OFF. Multiple repetitions of these three fields are allowed. @@ -4061,8 +4077,8 @@ Simple use of <makevar>OPTIONS</makevar> - OPTIONS= FOO "Enable option foo" On \ - BAR "Support feature bar" Off + OPTIONS= FOO "Enable option foo" On \ + BAR "Support feature bar" Off .include <bsd.port.options.mk> @@ -4076,12 +4092,12 @@ RUN_DEPENDS+= bar:${PORTSDIR}/bar/bar .endif -.include <bsd.port.mk> +.include <bsd.port.mk> Old style use of <makevar>OPTIONS</makevar> - OPTIONS= FOO "Enable option foo" On + OPTIONS= FOO "Enable option foo" On .include <bsd.port.pre.mk> @@ -4091,7 +4107,7 @@ CONFIGURE_ARGS+= --with-foo .endif -.include <bsd.port.post.mk> +.include <bsd.port.post.mk> @@ -4148,8 +4164,8 @@ ${DISTNAME}. In other words, if you have set: - PORTNAME= foo -PORTVERSION= 1.0 + PORTNAME= foo +PORTVERSION= 1.0 then the port's distribution files contain a top-level directory, foo-1.0, and the rest of the files are located @@ -4166,11 +4182,11 @@ extracted into a directory called foo (and not foo-1.0) you would write: - WRKSRC= ${WRKDIR}/foo + WRKSRC= ${WRKDIR}/foo or possibly - WRKSRC= ${WRKDIR}/${PORTNAME} + WRKSRC= ${WRKDIR}/${PORTNAME} @@ -4180,7 +4196,7 @@ you should set NO_WRKSUBDIR to indicate that. - NO_WRKSUBDIR= yes + NO_WRKSUBDIR= yes @@ -4483,7 +4499,7 @@ A typical example of utilizing PORTDOCS looks as follows: - PORTDOCS= README.* ChangeLog docs/* + PORTDOCS= README.* ChangeLog docs/* The equivalents of PORTDOCS for files @@ -4552,7 +4568,7 @@ de-installation will not cause the system to still believe the library is there. - USE_LDCONFIG= yes + USE_LDCONFIG= yes If you need, you can override the default directory by setting the USE_LDCONFIG @@ -4564,7 +4580,7 @@ you could use the following in your Makefile: - USE_LDCONFIG= ${PREFIX}/lib/foo ${PREFIX}/lib/bar + USE_LDCONFIG= ${PREFIX}/lib/foo ${PREFIX}/lib/bar Please double-check, often this is not necessary at all or can be avoided @@ -4703,10 +4719,11 @@ Examples The preferred way to state "the distfiles for this port must be - fetched manually" is as follows: -.if !exists(${DISTDIR}/${DISTNAME}${EXTRACT_SUFX}) -IGNORE= may not be redistributed because of licensing reasons. Please visit some-website to accept their license and download ${DISTFILES} into ${DISTDIR} -.endif + fetched manually" is as follows: + + .if !exists(${DISTDIR}/${DISTNAME}${EXTRACT_SUFX}) +IGNORE= may not be redistributed because of licensing reasons. Please visit some-website to accept their license and download ${DISTFILES} into ${DISTDIR} +.endif This both informs the user, and sets the proper metadata on the user's machine for use by automated programs. @@ -4946,7 +4963,7 @@ an individual port can make use of these tools via a simple construct: - USE_AUTOTOOLS= tool:version[:operation] ... + USE_AUTOTOOLS= tool:version[:operation] ... At the time of writing, tool can be one of libtool, libltdl, @@ -4984,7 +5001,7 @@ you need to use external libtool, you can use the version provided by The Ports Collection: - USE_AUTOTOOLS= libtool:version[:env] + USE_AUTOTOOLS= libtool:version[:env] With no additional operations, libtool:version tells @@ -5016,7 +5033,7 @@ libtool itself, so a separate construct is provided. - USE_AUTOTOOLS= libltdl:version + USE_AUTOTOOLS= libltdl:version Currently, all this does is to bring in a LIB_DEPENDS on the appropriate @@ -5136,21 +5153,21 @@ CPPFLAGS and LDFLAGS as follows: - USE_GETTEXT= yes -CPPFLAGS+= -I${LOCALBASE}/include -LDFLAGS+= -L${LOCALBASE}/lib + USE_GETTEXT= yes +CPPFLAGS+= -I${LOCALBASE}/include +LDFLAGS+= -L${LOCALBASE}/lib -GNU_CONFIGURE= yes -CONFIGURE_ENV= CPPFLAGS="${CPPFLAGS}" \ - LDFLAGS="${LDFLAGS}" +GNU_CONFIGURE= yes +CONFIGURE_ENV= CPPFLAGS="${CPPFLAGS}" \ + LDFLAGS="${LDFLAGS}" Of course, the code can be more compact if there are no more flags to pass to configure: - USE_GETTEXT= yes -GNU_CONFIGURE= yes -CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \ - LDFLAGS="-L${LOCALBASE}/lib" + USE_GETTEXT= yes +GNU_CONFIGURE= yes +CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include" \ + LDFLAGS="-L${LOCALBASE}/lib" @@ -5165,14 +5182,14 @@ For ports of low to medium complexity, you can rely on the following idiom: - GNU_CONFIGURE= yes + GNU_CONFIGURE= yes .if !defined(WITHOUT_NLS) -USE_GETTEXT= yes -PLIST_SUB+= NLS="" +USE_GETTEXT= yes +PLIST_SUB+= NLS="" .else -CONFIGURE_ARGS+= --disable-nls -PLIST_SUB+= NLS="@comment " +CONFIGURE_ARGS+= --disable-nls +PLIST_SUB+= NLS="@comment " .endif The next item on your to-do list is to arrange so that @@ -5392,8 +5409,8 @@ USE_XORG example - USE_XORG= xrender xft xkbfile xt xaw -USE_GL= glu + USE_XORG= xrender xft xkbfile xt xaw +USE_GL= glu Many ports define USE_XLIB, which makes @@ -5548,10 +5565,10 @@ Using X11 related variables in port # Use some X11 libraries and depend on # font server as well as cyrillic fonts. -RUN_DEPENDS= ${LOCALBASE}/bin/xfs:${X_FONTSERVER_PORT} \ - ${LOCALBASE}/lib/X11/fonts/cyrillic/crox1c.pcf.gz:${X_FONTS_CYRILLIC_PORT} +RUN_DEPENDS= ${LOCALBASE}/bin/xfs:${X_FONTSERVER_PORT} \ + ${LOCALBASE}/lib/X11/fonts/cyrillic/crox1c.pcf.gz:${X_FONTS_CYRILLIC_PORT} -USE_XORG= x11 xpm +USE_XORG= x11 xpm @@ -5618,7 +5635,7 @@ X server. The working DISPLAY is then passed to the build. - USE_DISPLAY= yes + USE_DISPLAY= yes @@ -5634,7 +5651,7 @@ be created, installed, and added to the pkg-plist automatically. Syntax is: - DESKTOP_ENTRIES= "NAME" "COMMENT" "ICON" "COMMAND" "CATEGORY" StartupNotify + DESKTOP_ENTRIES= "NAME" "COMMENT" "ICON" "COMMAND" "CATEGORY" StartupNotify The list of possible categories is available on the Freedesktop @@ -5644,10 +5661,10 @@ Example: - DESKTOP_ENTRIES= "ToME" "Roguelike game based on JRR Tolkien's work" \ - "${DATADIR}/xtra/graf/tome-128.png" \ - "tome -v -g" "Application;Game;RolePlaying;" \ - false + DESKTOP_ENTRIES= "ToME" "Roguelike game based on JRR Tolkien's work" \ + "${DATADIR}/xtra/graf/tome-128.png" \ + "tome -v -g" "Application;Game;RolePlaying;" \ + false @@ -5776,18 +5793,18 @@ When USE_QT_VER is set, some useful settings are passed to configure script: - CONFIGURE_ARGS+= --with-qt-includes=${QT_PREFIX}/include \ - --with-qt-libraries=${QT_PREFIX}/lib \ - --with-extra-libs=${LOCALBASE}/lib \ - --with-extra-includes=${LOCALBASE}/include -CONFIGURE_ENV+= MOC="${MOC}" CPPFLAGS="${CPPFLAGS} ${QTCPPFLAGS}" LIBS="${QTCFGLIBS}" \ - QTDIR="${QT_PREFIX}" KDEDIR="${KDE_PREFIX}" + CONFIGURE_ARGS+= --with-qt-includes=${QT_PREFIX}/include \ + --with-qt-libraries=${QT_PREFIX}/lib \ + --with-extra-libs=${LOCALBASE}/lib \ + --with-extra-includes=${LOCALBASE}/include +CONFIGURE_ENV+= MOC="${MOC}" CPPFLAGS="${CPPFLAGS} ${QTCPPFLAGS}" LIBS="${QTCFGLIBS}" \ + QTDIR="${QT_PREFIX}" KDEDIR="${KDE_PREFIX}" If USE_QT_VER is set to 4, the following settings are also deployed: - CONFIGURE_ENV+= UIC="${UIC}" QMAKE="${QMAKE}" QMAKESPEC="${QMAKESPEC}" -MAKE_ENV+= QMAKESPEC="${QMAKESPEC}" + CONFIGURE_ENV+= UIC="${UIC}" QMAKE="${QMAKE}" QMAKESPEC="${QMAKESPEC}" +MAKE_ENV+= QMAKESPEC="${QMAKESPEC}" @@ -5956,8 +5973,8 @@ qmake are only needed at buildtime, thus they are specified with the _build suffix: - USE_QT_VER= 4 -QT_COMPONENTS= gui moc_build qmake_build rcc_build uic_build + USE_QT_VER= 4 +QT_COMPONENTS= gui moc_build qmake_build rcc_build uic_build @@ -5971,8 +5988,8 @@ HAS_CONFIGURE= yes do-configure: - @cd ${WRKSRC} && ${SETENV} ${CONFIGURE_ENV} \ - ${QMAKE} -unix PREFIX=${PREFIX} texmaker.pro + @cd ${WRKSRC} && ${SETENV} ${CONFIGURE_ENV} \ + ${QMAKE} -unix PREFIX=${PREFIX} texmaker.pro Note the similarity to the qmake line from the provided BUILD.sh script. Passing @@ -6151,10 +6168,10 @@ If port requires some of Qt4 components, USE_QT_VER should be set and then needed components can be specified. - USE_CMAKE= yes -USE_KDE4= automoc4 kdelibs kdeprefix -USE_QT_VER= 4 -QT_COMPONENTS= qmake_build moc_build rcc_build uic_build + USE_CMAKE= yes +USE_KDE4= automoc4 kdelibs kdeprefix +USE_QT_VER= 4 +QT_COMPONENTS= qmake_build moc_build rcc_build uic_build @@ -6459,7 +6476,7 @@ statement (where myport.jar is the name of the JAR file installed as part of the port): - PLIST_FILES+= %%JAVAJARDIR%%/myport.jar + PLIST_FILES+= %%JAVAJARDIR%%/myport.jar When porting a Java application, the port usually installs everything under a single directory (including its JAR @@ -6802,26 +6819,26 @@ Example Makefile for PEAR class - PORTNAME= Date -PORTVERSION= 1.4.3 -CATEGORIES= devel www pear + PORTNAME= Date +PORTVERSION= 1.4.3 +CATEGORIES= devel www pear -MAINTAINER= example@domain.com -COMMENT= PEAR Date and Time Zone Classes +MAINTAINER= example@domain.com +COMMENT= PEAR Date and Time Zone Classes -BUILD_DEPENDS= ${PEARDIR}/PEAR.php:${PORTSDIR}/devel/pear-PEAR >>> TRUNCATED FOR MAIL (1000 lines) <<<