From owner-svn-doc-head@FreeBSD.ORG Sun Dec 8 18:04:02 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BB45B5C; Sun, 8 Dec 2013 18:04:02 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 359F51365; Sun, 8 Dec 2013 18:04:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rB8I42MF081307; Sun, 8 Dec 2013 18:04:02 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.7/Submit) id rB8I4296081305; Sun, 8 Dec 2013 18:04:02 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201312081804.rB8I4296081305@svn.freebsd.org> From: Warren Block Date: Sun, 8 Dec 2013 18:04:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43302 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 18:04:02 -0000 Author: wblock Date: Sun Dec 8 18:04:01 2013 New Revision: 43302 URL: http://svnweb.freebsd.org/changeset/doc/43302 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml head/en_US.ISO8859-1/books/porters-handbook/uses.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/book.xml Sun Dec 8 16:29:37 2013 (r43301) +++ head/en_US.ISO8859-1/books/porters-handbook/book.xml Sun Dec 8 18:04:01 2013 (r43302) @@ -9,11 +9,18 @@ $FreeBSD$ --> - - FreeBSD Porter's Handbook + + + + + FreeBSD Porter's Handbook - The FreeBSD Documentation Project + + The FreeBSD Documentation Project + $FreeBSD$ @@ -129,9 +136,10 @@ &prompt.root; echo DEVELOPER=yes >> /etc/make.conf - This setting enables the developer mode that - displays deprecation warnings and activates some further quality - checks on calling the make command. + This setting enables the developer mode + that displays deprecation warnings and activates some further + quality checks on calling the make + command. @@ -361,16 +369,16 @@ PLIST_DIRS= lib/X11/oneko The port can be deinstalled properly using the - deinstall target. This verifies - that the deinstall script works correctly. + deinstall target. This + verifies that the deinstall script works correctly. Make sure that make package can be run as a normal user (that is, not as - root). If that fails, - NEED_ROOT=yes must be added to the - port Makefile. + root). If that + fails, NEED_ROOT=yes must be added to + the port Makefile. @@ -413,11 +421,13 @@ PLIST_DIRS= lib/X11/onekoMake certain no warnings are shown in any of the stages. - Thorough automated testing can be done with ports-mgmt/tinderbox or - ports-mgmt/poudriere from the Ports Collection. - These applications maintain + Thorough automated testing can be done with + ports-mgmt/tinderbox or + ports-mgmt/poudriere from the Ports + Collection. These applications maintain jails where all of the steps shown above - can be tested without affecting the state of the host system. + can be tested without affecting the state of the host + system. @@ -455,7 +465,8 @@ PLIST_DIRS= lib/X11/onekoInclude your oneko.shar file in a bug report and send it with the &man.send-pr.1; program (see - Bug + Bug Reports and General Commentary for more information about &man.send-pr.1;). Be sure to classify the bug report as category ports and class @@ -485,12 +496,14 @@ PLIST_DIRS= lib/X11/onekoAfter you have submitted your port, please be patient. Sometimes it can take a few months before a port is included in &os;, although it might only take a few days. You can - view the list of ports + view the list of ports PRs waiting to be committed to &os;. Once we have looked at your port, we will get back to you if necessary, and put it in the tree. Your name will also - be added to the list of Additional + be added to the list of Additional FreeBSD Contributors and other files. @@ -518,20 +531,20 @@ PLIST_DIRS= lib/X11/oneko - The fetch target is run. The - fetch target is responsible for - making sure that the tarball exists locally in + The fetch target is run. + The fetch target is responsible + for making sure that the tarball exists locally in DISTDIR. If fetch cannot find the required files in DISTDIR it will look up the URL MASTER_SITES, which is set in the - Makefile, as well as our FTP mirrors - where we put distfiles as backup. It will then - attempt to fetch the named distribution file with - FETCH, assuming that the requesting - site has direct access to the Internet. If that succeeds, - it will save the file in DISTDIR for - future use and proceed. + Makefile, as well as our FTP mirrors where we put + distfiles as backup. It will then attempt to fetch the + named distribution file with FETCH, + assuming that the requesting site has direct access to the + Internet. If that succeeds, it will save the file in + DISTDIR for future use and + proceed. @@ -555,8 +568,8 @@ PLIST_DIRS= lib/X11/oneko - The configure target is run. - This can do any one of many different things. + The configure target is + run. This can do any one of many different things. @@ -582,11 +595,12 @@ PLIST_DIRS= lib/X11/oneko - The stage target is run. This - puts the final set of built files into a temporary directory - (STAGEDIR, see ). The hierarchy of this directory - mirrors that of the system on which the package will be - installed. + The stage target is run. + This puts the final set of built files into a temporary + directory (STAGEDIR, see + ). The hierarchy of this + directory mirrors that of the system on which the package + will be installed. @@ -680,8 +694,8 @@ PLIST_DIRS= lib/X11/onekoftp.FreeBSD.org; however, this is the least-preferred solution. The distfile must be placed into ~/public_distfiles/ of someone's - freefall account. Ask the person who commits - your port to do this. This person will also set + freefall account. Ask the person who + commits your port to do this. This person will also set MASTER_SITES to MASTER_SITE_LOCAL and MASTER_SITE_SUBDIR to their @@ -843,9 +857,9 @@ PLIST_DIRS= lib/X11/onekoUSES= dos2unix DOS2UNIX_REGEX= .*\.([ch]|cpp) - A similar option is DOS2UNIX_GLOB, which - invokes find for each element listed in - it. + A similar option is DOS2UNIX_GLOB, + which invokes find for each element listed + in it. USES= dos2unix DOS2UNIX_GLOB= *.c *.cpp *.h @@ -854,8 +868,8 @@ DOS2UNIX_GLOB= *.c *.cpp *.h.orig extension, and then modify the original one. The makepatch target - will write out an appropriate patch file to the files directory of the - port. + will write out an appropriate patch file to the + files directory of the port. @@ -1327,9 +1341,10 @@ PORTEPOCH= 1 - If the port can be built with different hardcoded defaults - (usually part of the directory name in a family of - ports), the + If the port can be built with different + hardcoded + defaults (usually part of the directory name in + a family of ports), the -compiled.specifics part should state the compiled-in defaults (the hyphen is optional). Examples are paper size and font @@ -1581,7 +1596,9 @@ PORTEPOCH= 1 afterstep* - Ports to support the AfterStep + + Ports to support the AfterStep window manager. @@ -1925,7 +1942,9 @@ PORTEPOCH= 1 palm - Software support for the Palm™ + + Software support for the Palm™ series. @@ -1954,7 +1973,9 @@ PORTEPOCH= 1 plan9* - Various programs from Plan9. + + Various programs from Plan9. @@ -1985,21 +2006,26 @@ PORTEPOCH= 1 python* - Software related to the Python + + Software related to the Python language. ruby* - Software related to the Ruby + Software related to the Ruby language. rubygems* - Ports of RubyGems + + Ports of RubyGems packages. @@ -2163,7 +2189,8 @@ PORTEPOCH= 1 zope* - Zope + Zope support. @@ -2283,15 +2310,16 @@ PORTEPOCH= 1 human languages), or preferably both. The rationale for this is that such a change creates a - fair - amount of work for both the committers and also - for all users who track changes to the Ports Collection. In + fair + amount of work for both the committers and also for + all users who track changes to the Ports Collection. In addition, proposed category changes just naturally seem to attract controversy. (Perhaps this is because there is no - clear consensus on when a category is too - big, nor whether categories should lend themselves - to browsing (and thus what number of categories would be an - ideal number), and so forth.) + clear consensus on when a category is + too big, nor whether categories should lend + themselves to browsing (and thus what number of categories + would be an ideal number), and so forth.) Here is the procedure: @@ -2356,8 +2384,9 @@ PORTEPOCH= 1 If that PR is approved, a committer will need to - follow the rest of the procedure that is - outlined in the Committer's Guide. + follow the rest of the procedure that is outlined + in the Committer's Guide. @@ -2812,9 +2841,12 @@ EXTRACT_ONLY= source.tar.gzsource2.tar.gz, which must be downloaded from two different sites. The port's Makefile would include lines like - . + . + + - Simplified Use of <literal>MASTER_SITES:n</literal> with One File Per Site @@ -2830,9 +2862,12 @@ DISTFILES= source1.tar.gz:source1 \ should be downloaded from ftp.example2.com. The Makefile would then be written like - . + . + + - Simplified Use of <literal>MASTER_SITES:n</literal> with More Than One File Per Site @@ -2872,9 +2907,11 @@ DISTFILES= source1.tar.gz:source1 \ postfixing purposes since they yield special meaning: default, all and ALL (they are used internally in - item ). + item ). Furthermore, DEFAULT is a special - purpose word (check item ). + purpose word (check item ). @@ -2891,7 +2928,8 @@ DISTFILES= source1.tar.gz:source1 \ elements with DEFAULT, you are just being redundant unless you want to have an element belonging to both DEFAULT and other - groups at the same time (check item ). + groups at the same time (check item ). The following examples are equivalent but the first one is preferred: @@ -2960,9 +2998,8 @@ DISTFILES= source1.tar.gz:source1 \ be terminated with the forward slash / character. If any elements belong to any groups, the group postfix - :n - must come right after the terminator - /. The + :n must come right after the + terminator /. The MASTER_SITES:n mechanism relies on the existence of the terminator / to avoid confusing elements @@ -2974,15 +3011,18 @@ DISTFILES= source1.tar.gz:source1 \ required before in both MASTER_SITE_SUBDIR and PATCH_SITE_SUBDIR elements, if - the postfix immediate preceding character is not - a / then :n + the postfix immediate preceding character is not a + / then :n will be considered a valid part of the element instead of a group postfix even if an element is postfixed with :n. See both - - and . + + and . - + Detailed Use of <literal>MASTER_SITES:n</literal> in @@ -3004,7 +3044,9 @@ DISTFILES= source1.tar.gz:source1 \ </itemizedlist> </example> - <example xml:id="ports-master-sites-n-example-detailed-use-complete-example-master-sites"> + <example + xml:id="ports-master-sites-n-example-detailed-use-complete-example-master-sites"> + <title>Detailed Use of <literal>MASTER_SITES:n</literal> with Comma Operator, Multiple Files, Multiple Sites and @@ -3199,9 +3241,12 @@ MASTER_SITE_SUBDIR= directory-trial:1 di <filename>bsd.sites.mk</filename>, e.g., <varname>MASTER_SITE_SOURCEFORGE</varname>?</para> - <para>See <xref linkend="ports-master-sites-n-example-detailed-use-master-site-sourceforge"/>.</para> + <para>See <xref + linkend="ports-master-sites-n-example-detailed-use-master-site-sourceforge"/>.</para> + + <example + xml:id="ports-master-sites-n-example-detailed-use-master-site-sourceforge"> - <example xml:id="ports-master-sites-n-example-detailed-use-master-site-sourceforge"> <title>Detailed Use of <literal>MASTER_SITES:n</literal> with <varname>MASTER_SITE_SOURCEFORGE</varname> @@ -3222,9 +3267,12 @@ DISTFILES= something.tar.gz:sourceforge< All examples were done with MASTER* variables but they work exactly the same for PATCH* ones as - can be seen in . + can be seen in . + + - Simplified Use of <literal>MASTER_SITES:n</literal> with <varname>PATCH_SITES</varname> @@ -3244,27 +3292,30 @@ PATCHFILES= patch1:test All current ports remain the same. The MASTER_SITES:n feature code is only activated if there are elements postfixed with - :n like - elements according to the aforementioned syntax rules, - especially as shown in item . + :n like elements according to the + aforementioned syntax rules, especially as shown in + item . - + The port targets remain the same: checksum, makesum, patch, configure, - build, etc. With the obvious - exceptions of do-fetch, + build, etc. With the + obvious exceptions of + do-fetch, fetch-list, master-sites and patch-sites. - do-fetch: deploys the - new grouping postfixed + do-fetch: deploys + the new grouping postfixed DISTFILES and PATCHFILES with their matching group elements within both @@ -3272,13 +3323,14 @@ PATCHFILES= patch1:test PATCH_SITES which use matching group elements within both MASTER_SITE_SUBDIR and - PATCH_SITE_SUBDIR. Check . + PATCH_SITE_SUBDIR. Check . fetch-list: works - like old fetch-list with - the exception that it groups just like + like old fetch-list + with the exception that it groups just like do-fetch. @@ -3286,10 +3338,10 @@ PATCHFILES= patch1:test master-sites and patch-sites: (incompatible with older versions) only return the - elements of group DEFAULT; in + elements of group DEFAULT; in fact, they execute targets - master-sites-default and - patch-sites-default + master-sites-default + and patch-sites-default respectively. Furthermore, using target either @@ -3299,7 +3351,8 @@ PATCHFILES= patch1:test MASTER_SITES or PATCH_SITES. Also, directly checking is not guaranteed to work in any - future versions. Check item + future versions. Check item for more information on these new port targets. @@ -3320,20 +3373,21 @@ PATCHFILES= patch1:test within MASTER_SITES and PATCH_SITES respectively. For instance, both - master-sites-DEFAULT and - patch-sites-DEFAULT will - return the elements of group + master-sites-DEFAULT + and patch-sites-DEFAULT + will return the elements of group DEFAULT, master-sites-test and - patch-sites-test of group - test, and thereon. + patch-sites-test of + group test, and thereon. - + There are new targets master-sites-all and - patch-sites-all which do - the work of the old + patch-sites-all which + do the work of the old master-sites and patch-sites ones. They return the elements of all groups as if they all @@ -3343,7 +3397,7 @@ PATCHFILES= patch1:test MASTER_SITE_OVERRIDE as there are groups defined within either DISTFILES or - PATCHFILES; respectively for + PATCHFILES; respectively for master-sites-all and patch-sites-all. @@ -3397,7 +3451,9 @@ PATCHFILES= patch1:test add the source distfiles to DISTFILES when PACKAGE_BUILDING is defined. - + + Use of <varname>ALWAYS_KEEP_DISTFILES</varname> @@ -3419,8 +3475,9 @@ ALWAYS_KEEP_DISTFILES= yes <varname>MAINTAINER</varname> - Set your mail-address here. Please. :-) + Set your mail-address here. Please. + + :-) Note that only a single address without the comment part is allowed as a MAINTAINER value. The @@ -3430,9 +3487,10 @@ ALWAYS_KEEP_DISTFILES= yes bsd.port.mk. The maintainer is responsible for keeping the port up to - date, and ensuring the port works correctly. - For a detailed description of the responsibilities of a port - maintainer, refer to the The + date, and ensuring the port works correctly. For a detailed + description of the responsibilities of a port maintainer, + refer to the The challenge for port maintainers section. Changes to the port will be sent to the maintainer of a @@ -3597,8 +3655,8 @@ ALWAYS_KEEP_DISTFILES= yes The dependency is checked twice, once from within the build target and then from within - the install target. Also, the name - of the dependency is put into the package so that + the install target. Also, the + name of the dependency is put into the package so that &man.pkg.add.1; will automatically install it if it is not on the user's system. @@ -3651,8 +3709,8 @@ ALWAYS_KEEP_DISTFILES= yes The dependency is checked from within the - install target. Also, the name of - the dependency is put into the package so that + install target. Also, the name + of the dependency is put into the package so that &man.pkg.add.1; will automatically install it if it is not on the user's system. The target part can be omitted if it is the same as @@ -3794,7 +3852,8 @@ ALWAYS_KEEP_DISTFILES= yes USES= feature[:arguments] - For the complete list of such values, please see . + For the complete list of such values, please see + . USES cannot be assigned after @@ -3983,7 +4042,8 @@ ALWAYS_KEEP_DISTFILES= yes Problems Caused by Automatic Dependencies Dependencies must be declared either explicitly or by - using the OPTIONS framework. + using the + OPTIONS framework. Using other methods like automatic detection complicates indexing, which causes problems for port and package management. @@ -4079,7 +4139,8 @@ LIB_DEPENDS= libbar.so:${PORTSDIR}/foo/b In the sole Makefile, you can use MASTERDIR to specify the directory where the rest of the files are. Also, use a variable as part of - PKGNAMESUFFIX + PKGNAMESUFFIX so the packages will have different names. This will be best demonstrated by an example. This is @@ -4132,11 +4193,11 @@ MASTERDIR= ${.CURDIR}/../xdvi300 If your port anchors its man tree somewhere other than PREFIX, you can use MANDIRS to specify those directories. Note - that the files corresponding to manual pages should be placed in - pkg-plist along with the rest of the files. - The purpose of MANDIRS is to enable automatic - compression of manual pages, therefore the file names should be - suffixed with .gz. + that the files corresponding to manual pages should be placed + in pkg-plist along with the rest of the + files. The purpose of MANDIRS is to enable + automatic compression of manual pages, therefore the file + names should be suffixed with .gz. @@ -4187,7 +4248,8 @@ MASTERDIR= ${.CURDIR}/../xdvi300 These variables are designed to be set by the system administrator. There are many that are standardized in - the ports/KNOBS + the ports/KNOBS file. When creating a port, do not make knob names specific @@ -4246,10 +4308,11 @@ MASTERDIR= ${.CURDIR}/../xdvi300 Knob Naming - Porters should use like-named knobs, both - for the benefit of end-users and to help keep the number - of knob names down. A list of popular knob names can be - found in the KNOBS + Porters should use like-named knobs, both for the + benefit of end-users and to help keep the number of knob + names down. A list of popular knob names can be found in + the KNOBS file. Knob names should reflect what the knob is and does. @@ -4962,16 +5025,15 @@ PORTVERSION= 1.0 Use the macros provided in bsd.port.mk to ensure correct modes of - files in the port's *-install targets. - Set ownership directly in + files in the port's *-install + targets. Set ownership directly in pkg-plist with the corresponding - entries, such as @owner - owner and @group - group. These - operators work until being overridden, or until the end of - pkg-plist, so do not forget to reset them - after they are no longer needed. The default - ownership is root:wheel. + entries, such as @owner owner and + @group group. These operators work until + being overridden, or until the end of + pkg-plist, so do not forget to reset + them after they are no longer needed. The default ownership + is root:wheel. @@ -5046,14 +5108,14 @@ PORTVERSION= 1.0 Installing a Whole Tree of Files Sometimes, a large number of - files must be installed while preserving their hierarchical organization. For example, - copying over a whole directory tree from - WRKSRC to a target directory under - PREFIX. Note that + files must be installed while preserving their hierarchical + organization. For example, copying over a whole directory + tree from WRKSRC to a target directory + under PREFIX. Note that PREFIX, EXAMPLESDIR, - DATADIR, and other path varialbes must always be - prepended with STAGEDIR to respect - staging (see ). + DATADIR, and other path varialbes must + always be prepended with STAGEDIR to + respect staging (see ). Two macros exist for this situation. The advantage of using these macros instead of cp is that @@ -5097,9 +5159,10 @@ PORTVERSION= 1.0 ${COPYTREE_SHARE} . ${STAGEDIR}${EXAMPLESDIR} "! -name Makefile") These macros do not add the installed files - to pkg-plist. They must be added manually. - For optional documentation - (PORTDOCS, see ) and examples + to pkg-plist. They must be added + manually. For optional documentation + (PORTDOCS, see + ) and examples (PORTEXAMPLES), the %%PORTDOCS%% or %%PORTEXAMPLES%% prefixes must be @@ -5126,9 +5189,10 @@ PORTVERSION= 1.0 Since only the files listed in pkg-plist are installed, it is safe to always install documentation to STAGEDIR - (see ). Hence .if - blocks are only needed when the installed files are - large enough to cause significant I/O overhead. + (see ). Hence + .if blocks are only needed when the + installed files are large enough to cause significant I/O + overhead. post-install: ${MKDIR} ${STAGEDIR}${DOCSDIR} @@ -5274,19 +5338,20 @@ PORTVERSION= 1.0 Staging - bsd.port.mk expects ports to work with - a stage directory. This means that a - port should not install files directly to the regular - destination directories (that is, under - PREFIX, for example) but instead into a - separate directory from which the package is then built. In - many cases, this does not require root privileges, making it - possible to build packages as an unprivileged user. With - staging, the port is built and installed into the stage - directory, STAGEDIR. A package is created - from the stage directory and then installed on the system. Automake tools refer to - this concept as DESTDIR, but in &os;, - DESTDIR has a different meaning (see ). + bsd.port.mk expects ports to work + with a stage directory. This means that a port + should not install files directly to the regular destination + directories (that is, under PREFIX, for + example) but instead into a separate directory from which the + package is then built. In many cases, this does not require + root privileges, making it possible to build packages as an + unprivileged user. With staging, the port is built and + installed into the stage directory, + STAGEDIR. A package is created from the + stage directory and then installed on the system. Automake + tools refer to this concept as DESTDIR, but + in &os;, DESTDIR has a different meaning + (see ). When a port still requires system-wide privileges in order to run the package target, this @@ -5296,38 +5361,40 @@ PORTVERSION= 1.0 NEED_ROOT= yes Meta ports, or ports that do not install files themselves - but only depend on other ports, should avoid - needlessly extracting the &man.mtree.8; to the stage directory. - This is the basic directory layout - of the package, and these empty directories will be seens as - orphans. To prevent &man.mtree.8; extraction, add this line: + but only depend on other ports, should avoid needlessly + extracting the &man.mtree.8; to the stage directory. This is + the basic directory layout of the package, and these empty + directories will be seens as orphans. To prevent + &man.mtree.8; extraction, add this line: NO_MTREE= yes Staging is enabled by prepending the - STAGEDIR variable to paths used in - the pre-install, + STAGEDIR variable to paths used in the + pre-install, do-install, and - post-install targets (see the examples - through the book). Typically, this includes + post-install targets (see the + examples through the book). Typically, this includes PREFIX, ETCDIR, DATADIR, EXAMPLESDIR, - MANPREFIX, DOCSDIR, and so on. - Directories should be created as part of the + MANPREFIX, DOCSDIR, and + so on. Directories should be created as part of the post-install target. Avoid using absolute paths whenever possible. - When creating a symlink, STAGEDIR should - be prepended to the target path only. For example: + When creating a symlink, STAGEDIR + should be prepended to the target path only. For + example: ${LN} -sf libfoo.so.42 ${STAGEDIR}${PREFIX}/lib/libfoo.so The source path - ${PREFIX}/lib/libfoo.so.42 looks - fine but could, in fact, be incorrect. Absolute paths can - point to a wrong location, like when a remote - file system has been mounted with NFS under a non-root mount point. - Relative paths are less fragile, and often much shorter. + ${PREFIX}/lib/libfoo.so.42 looks fine but + could, in fact, be incorrect. Absolute paths can point to a + wrong location, like when a remote file system has been + mounted with NFS under a non-root mount + point. Relative paths are less fragile, and often much + shorter. Ports that install kernel modules must prepend the STAGEDIR variable to @@ -5605,9 +5672,10 @@ IGNORE= may not be redistributed because set. If your port's source Makefile has - something else than all as the main - build target, set ALL_TARGET accordingly. - Same goes for install and + something else than all as the + main build target, set ALL_TARGET + accordingly. Same goes for + install and INSTALL_TARGET. @@ -6138,7 +6206,8 @@ PLIST_SUB+= NLS="@comment " top-level hierarchy name. For example, the recommended value for p5-Module-Name is Module. The top-level hierarchy can be - examined at cpan.org. + examined at cpan.org. This keeps the port working when the author of the module changes. @@ -6260,8 +6329,8 @@ PLIST_SUB+= NLS="@comment " Ports of Perl modules which do not have an official - website should link to cpan.org in the WWW - line of pkg-descr. The + website should link to cpan.org in + the WWW line of pkg-descr. The preferred URL form is http://search.cpan.org/dist/Module-Name/ (including the trailing slash). @@ -6284,10 +6353,10 @@ PLIST_SUB+= NLS="@comment " For Perl ports that install manual pages, the macro - PERL5_MANx (where - x ranges from 1 to - 9) can be used inside - pkg-plist. For example, + PERL5_MANx + (where x ranges from + 1 to 9) can be used + inside pkg-plist. For example, lib/perl5/5.14/man/man3/AnyEvent::I3.3.gz @@ -6441,7 +6510,8 @@ USE_XORG= x11 xpm Desktop Entries - Desktop entries (a + Desktop entries (a Freedesktop standard) provide a way to automatically adjust desktop features when a new program is installed, without requiring user intervention. For @@ -6465,7 +6535,8 @@ USE_XORG= x11 xpm include those files in pkg-plist and install them in the $LOCALBASE/share/applications - directory. The INSTALL_DATA + directory. The INSTALL_DATA macro is useful for installing these files. @@ -6496,7 +6567,8 @@ USE_XORG= x11 xpm DESKTOP_ENTRIES= "NAME" "COMMENT" "ICON" "COMMAND" "CATEGORY" StartupNotify The list of possible categories is available on the - Freedesktop + Freedesktop website. StartupNotify indicates whether the application is compatible with startup notifications. These are @@ -6526,8 +6598,8 @@ USE_XORG= x11 xpm Using GNOME The FreeBSD/GNOME project uses its own set of variables to - define which GNOME components a particular port uses. A - comprehensive + define which GNOME components a particular port uses. A comprehensive list of these variables exists within the FreeBSD/GNOME project's homepage. @@ -6863,8 +6935,9 @@ PLIST_SUB+= QT_INCDIR_REL=${QT_INCDIR_RE QMAKE_PRO - Name of the project .pro file. - The default is empty (using autodetection). + Name of the project .pro + file. The default is empty (using + autodetection). @@ -7490,11 +7563,12 @@ USE_QT4= moc_build qmake_build rcc_build All the features that have been presented in this section are implemented in bsd.java.mk. If you ever think that your port needs more sophisticated - Java support, please first have a look at the bsd.java.mk - SVN log as it usually takes some time - to document the latest features. Then, if you think the - support you are lacking would be beneficial to many other - Java ports, feel free to discuss it on the &a.java;. + Java support, please first have a look at the bsd.java.mk + SVN log as it usually takes some time to document + the latest features. Then, if you think the support you are + lacking would be beneficial to many other Java ports, feel + free to discuss it on the &a.java;. Although there is a java category for PRs, it refers to the JDK porting effort from the &os; Java @@ -7531,7 +7605,8 @@ USE_QT4= moc_build qmake_build rcc_build etc. The default APACHE version is 22. More details are available in ports/Mk/bsd.apache.mk and - at wiki.freebsd.org/Apache/. *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***