From c16925d60c31dae0c1827ea6a94e5a7ec21ff7c6 Mon Sep 17 00:00:00 2001 From: Mathieu Arnold Date: Fri, 2 Mar 2018 09:03:47 +0000 Subject: [PATCH] Replaces occurrences of 0.0.yyyymmdd by dyyyymmdd. Sponsored by: Absolight --- .../porters-handbook/makefiles/chapter.xml | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml b/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml index 2ebcba4c2b..80b9651453 100644 --- a/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml +++ b/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml @@ -743,13 +743,14 @@ PORTEPOCH= 1 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 + dyyyy.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 + format. It is important to prefix the version with a + letter, here d (for date), in case a + release with an actual version number is made, which would be numerically less than yyyy. @@ -935,8 +936,18 @@ PORTEPOCH= 1 piewm example above). Otherwise, ask the original author or use the date string the source file was released on - (0.0.yyyy.mm.dd) + (dyyyy.mm.dd, + or + dyyyymmdd) as the version. + + + Use any letter. Here, d here stands + for date, if the source is a Git + repository, g followed by the commit date + is commonly used, using s for snapshot is + also common. +