CVS commit: pkgsrc/doc/guide/files

["Greg Troxel" <gdt%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   gdt
Date:           Thu Jun 30 14:04:32 UTC 2022

Modified Files:
        pkgsrc/doc/guide/files: using.xml

Log Message:
guide: using: Clean up old content

The "OS directories with versions" caution no longer applies; we don't
have any.   Soften the expectation of bootstrap kits, as packages on
cdn.n.o ~never have them.


To generate a diff of this commit:
cvs rdiff -u -r1.52 -r1.53 pkgsrc/doc/guide/files/using.xml

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/doc/guide/files/using.xml
diff -u pkgsrc/doc/guide/files/using.xml:1.52 pkgsrc/doc/guide/files/using.xml:1.53
--- pkgsrc/doc/guide/files/using.xml:1.52       Fri Jun 11 14:45:08 2021
+++ pkgsrc/doc/guide/files/using.xml    Thu Jun 30 14:04:32 2022
@@ -1,4 +1,4 @@
-<!-- $NetBSD: using.xml,v 1.52 2021/06/11 14:45:08 nia Exp $ -->
+<!-- $NetBSD: using.xml,v 1.53 2022/06/30 14:04:32 gdt Exp $ -->
 
 <chapter id="using"> <?dbhtml filename="using.html"?>
 <title>Using pkgsrc</title>
@@ -38,12 +38,11 @@ and you can still use binary packages fr
     url="https://cdn.NetBSD.org/pub/pkgsrc/packages/";><filename>/pub/pkgsrc/packages</filename></ulink>.</para>
 
     <para>This directory contains binary packages for multiple
-    platforms. First, select your operating system. (Ignore the
-    directories with version numbers attached to it, they just exist for
-    legacy reasons.) Then, select your hardware architecture, and in the
-    third step, the OS version and the <quote>version</quote> of pkgsrc.</para>
+    platforms. First, select your operating system. Then, select your
+    hardware architecture, and in the third step, the OS version and
+    the <quote>version</quote> of pkgsrc.</para>
 
-    <para>In this directory, you often find a file called
+    <para>In this directory, you may find a file called
     <filename>bootstrap.tar.gz</filename> which contains the package
     management tools. If the file is missing, it is likely that your
     operating system already provides those tools. Download the file and