From owner-svn-doc-head@FreeBSD.ORG Fri Apr 4 01:55:03 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1FE3F44; Fri, 4 Apr 2014 01:55: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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B311B9CF; Fri, 4 Apr 2014 01:55:02 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s341t2PK014776; Fri, 4 Apr 2014 01:55:02 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s341t233014775; Fri, 4 Apr 2014 01:55:02 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201404040155.s341t233014775@svn.freebsd.org> From: Warren Block Date: Fri, 4 Apr 2014 01:55:02 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44436 - head/en_US.ISO8859-1/books/porters-handbook/makefiles 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: Fri, 04 Apr 2014 01:55:03 -0000 Author: wblock Date: Fri Apr 4 01:55:02 2014 New Revision: 44436 URL: http://svnweb.freebsd.org/changeset/doc/44436 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Fri Apr 4 01:46:32 2014 (r44435) +++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Fri Apr 4 01:55:02 2014 (r44436) @@ -351,108 +351,120 @@ PORTEPOCH= 1 language_region- - - &os; strives to support the native language of its - users. The language- part - is a two letter abbreviation of the natural - language defined by ISO-639 when the port is specific to a - certain language. Examples are ja for - Japanese, ru for Russian, - vi for Vietnamese, - zh for Chinese, ko - for Korean and de for German. - - If the port is specific to a certain region within the - language area, add the two letter country code as well. - Examples are en_US for US English and - fr_CH for Swiss French. - - The language- part is - set in the PKGNAMEPREFIX - variable. - + + + &os; strives to support the native language of its + users. The language- part is + a two letter abbreviation of the natural language + defined by ISO-639 when the port is specific to a + certain language. Examples are ja + for Japanese, ru for Russian, + vi for Vietnamese, + zh for Chinese, ko + for Korean and de for German. + + If the port is specific to a certain region within + the language area, add the two letter country code as + well. Examples are en_US for US + English and fr_CH for Swiss + French. + + The language- part is + set in the PKGNAMEPREFIX + variable. + name - - The first letter of the name part - should be lowercase. (The rest of the name may contain - capital letters, so use your own discretion when - converting a software name that has some capital letters - in it.) There is a tradition of naming - Perl 5 modules by prepending - p5- and converting the double-colon - separator to a hyphen. For example, the - Data::Dumper module becomes - p5-Data-Dumper. - Make sure that the port's name and version are clearly - separated and placed into the PORTNAME - and PORTVERSION variables. The only - reason for PORTNAME to contain a - version part is if the upstream distribution is really - named that way, as in the - textproc/libxml2 or - japanese/kinput2-freewnn ports. - Otherwise, the PORTNAME should not - contain any version-specific information. It is quite - normal for several ports to have the same - PORTNAME, as the - www/apache* ports do; in that case, - different versions (and different index entries) are - distinguished by the PKGNAMEPREFIX and - PKGNAMESUFFIX values. - + + + The first letter of the name + part should be lowercase. (The rest of the name may + contain capital letters, so use your own discretion when + converting a software name that has some capital letters + in it.) There is a tradition of naming + Perl 5 modules by prepending + p5- and converting the double-colon + separator to a hyphen. For example, the + Data::Dumper module becomes + p5-Data-Dumper. + + Make sure that the port's name and version are + clearly separated and placed into the + PORTNAME and + PORTVERSION variables. The only + reason for PORTNAME to contain a + version part is if the upstream distribution is really + named that way, as in the + textproc/libxml2 or + japanese/kinput2-freewnn ports. + Otherwise, the PORTNAME should not + contain any version-specific information. It is quite + normal for several ports to have the same + PORTNAME, as the + www/apache* ports do; in that case, + different versions (and different index entries) are + distinguished by the PKGNAMEPREFIX + and PKGNAMESUFFIX values. + -compiled.specifics - - 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 units. - - The -compiled.specifics - part is set in the PKGNAMESUFFIX - variable. - + + + 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 + units. + + The -compiled.specifics + part is set in the PKGNAMESUFFIX + variable. + -version.numbers - - The version string follows a dash - (-) and is a period-separated list of - integers and single lowercase alphabetics. In particular, - it is not permissible to have another dash inside the - version string. The only exception is the string - pl (meaning patchlevel), - which can be used only when there are - no major and minor version numbers in the software. If - the software version has strings like - alpha, beta, - rc, or pre, take the first - letter and put it immediately after a period. If the - version string continues after those names, the numbers - should follow the single alphabet without an extra period - between them. - - The idea is to make it easier to sort ports by looking - at the version string. In particular, make sure version - number components are always delimited by a period, and if - the date is part of the string, use the - 0.0.yyyy.mm.dd format, not - dd.mm.yyyy or the non-Y2K compliant - yy.mm.dd format. It is important to - prefix the version with 0.0. in case a - release with an actual version number is made, which would - of course be numerically less than - yyyy. - + + + The version string follows a dash + (-) and is a period-separated list of + integers and single lowercase alphabetics. In + particular, it is not permissible to have another dash + inside the version string. The only exception is the + string pl (meaning + patchlevel), which can be used + only when there are no major and + minor version numbers in the software. If the software + version has strings like alpha, + beta, rc, or + pre, take the first letter and put it + immediately after a period. If the version string + continues after those names, the numbers should follow + the single alphabet without an extra period between + them. + + The idea is to make it easier to sort ports by + looking at the version string. In particular, make sure + version number components are always delimited by a + period, and if the date is part of the string, use the + 0.0.yyyy.mm.dd + format, not + dd.mm.yyyy + or the non-Y2K compliant + yy.mm.dd + format. It is important to prefix the version with + 0.0. in case a release with an actual + version number is made, which would of course be + numerically less than + yyyy. + @@ -604,7 +616,8 @@ PORTEPOCH= 1 string to 1.0 (like the piewm example above). Otherwise, ask the original author or use the date string - (0.0.yyyy.mm.dd) as the version. + (0.0.yyyy.mm.dd) + as the version. @@ -1992,8 +2005,9 @@ DISTFILES= source1.tar.gz:source1 \ - Elements can be postfixed with :n - where n is + Elements can be postfixed with + :n where + n is [^:,]+, i.e., n could conceptually be any alphanumeric string but we will limit it to @@ -2099,8 +2113,9 @@ 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 @@ -2392,9 +2407,9 @@ 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 . @@ -4257,16 +4272,16 @@ PORTVERSION= 1.0 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. + 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. - INSTALL_PROGRAM is a command to install binary executables.