From 353ee51fed783e723966c50d745ee20d0d7e6d01 Mon Sep 17 00:00:00 2001 From: rillig Date: Thu, 11 Oct 2007 21:03:39 +0000 Subject: Most of the bootstrap kits are out-dated. Provided more explanation for the naming of the subdirectories under packages/. Added reports/. --- doc/guide/files/ftp-layout.xml | 41 +++++++++++++++++++++++++++++++++++------ 1 file changed, 35 insertions(+), 6 deletions(-) (limited to 'doc/guide') diff --git a/doc/guide/files/ftp-layout.xml b/doc/guide/files/ftp-layout.xml index 76029f5590c..b730a105969 100644 --- a/doc/guide/files/ftp-layout.xml +++ b/doc/guide/files/ftp-layout.xml @@ -1,4 +1,4 @@ - + Directory layout of the pkgsrc FTP server @@ -18,7 +18,8 @@ For those who only want to manage binary packages on systems other than NetBSD, we provide the package management - tools in a separate, small tar file. + tools in a separate, small tar file. Please note that most of + these files are horribly outdated. @@ -56,10 +57,29 @@ >. The meaning of these variables is: - OPSYS is the name of the operating system for which the packages have been built, - ARCH is the hardware architecture, - OSVERSION is the version of the operating system, - TAG is either 200xQy for a stable branch, or head for packages built from the HEAD branch. + + OPSYS is the name of the + operating system for which the packages have been + built. + + ARCH is the hardware + architecture of the platform for which the packages have been + built. + + OSVERSION is the version of + the operating system. For version numbers that change often (for + example NetBSD-current), the often-changing part should be + replaced with an x, for example + 4.99.x. + + TAG is either + 200xQy + for a stable branch, or head for packages + built from the HEAD branch. The latter should only be used when + the packages are updated on a regular basis. Otherwise the date + from checking out pkgsrc should be appended, for example + head_20071015. + The rationale for exactly this scheme is that the pkgsrc users looking for binary packages @@ -77,6 +97,15 @@ Besides that, there are various category directories that contain symbolic links to the real binary packages. + + +<filename>reports</filename>: Bulk build reports + + Here are the reports from bulk builds, for those who want + to fix packages that didn't build on some of the platforms. The + structure of subdirectories should look like the one in . + <filename>current</filename>, -- cgit v1.2.3