[cygwin-apps htdocs - The cygwin-apps website files] branch master, updated. ce626d0b87fa14c76b7dd339b53f127002c35b9f

[jturney@sourceware.org]

https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=ce626d0b87fa14c76b7dd339b53f127002c35b9f

commit ce626d0b87fa14c76b7dd339b53f127002c35b9f
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Wed May 11 18:20:25 2016 +0000

    Update for noarch


Diff:
---
 package-upload.html |   28 +++++++++++++++++-----------
 1 files changed, 17 insertions(+), 11 deletions(-)

diff --git a/package-upload.html b/package-upload.html
index 0226562..f7058a4 100644
--- a/package-upload.html
+++ b/package-upload.html
@@ -85,12 +85,12 @@ packages, the easiest way to upload your finished packages is just to run:<p>
 directory on cygwin.com will look like this:</p>
 
 <pre>
-    Your Name                   # Directory is currently your full name (you won't actually see this)
-        !packages               # read-only file containing valid packages
-        x86        x86_64       # arch-specific dir
-        release    release      # release dir
-          pkg                   # package directory
-           pkg-debuginfo        # package subdirectories
+       Your Name                          # directory is currently your full name (you won't actually see this)
+        !packages                         # read-only file containing package names you are permitted to upload
+        x86        x86_64    noarch       # arch directory
+         release    release   release     # release directory
+          pkg                             # package directory
+           pkg-debuginfo                  # package subdirectories
 </pre>
 
 <h4>Example using <a href="http://lftp.yar.ru/">lftp</a> to upload packages:</h4>
@@ -164,9 +164,10 @@ than this file in or under the given directory should be processed.  The
 intent is that you create <tt>!ready</tt> when you have finished
 uploading everything that you plan on uploading.</p>
 
-<p><b>Note: <tt>!ready</tt> files need to be created at least once for each
-architecture that is uploaded</b>, i.e., in each of the <tt>x86</tt> and
-<tt>x86_64</tt> directories or in the package directories themselves.</p>
+<p><b>Note: <tt>!ready</tt> files should not be created in the root of your
+upload directory</b>, i.e. they should be in the architecture
+directories <tt>x86</tt>, <tt>x86_64</tt> and <tt>noarch</tt> or in the package
+directories themselves.</p>
 
 <p><tt>calm</tt> will periodically scan the upload directories for
 packages that are ready, and, if there are no errors, move the packages
@@ -184,13 +185,18 @@ uploaded.  This file must be in the root of your upload directory.</p>
 
 <h2><a name="deleting">Removing files from the Cygwin distribution</a></h2>
 
-To cause files to be removed from the distribution, upload an empty file with the name of the file that you want deleted, prefixed with a "<tt>-</tt>".
+Removing files is not normally needed, as old versions which aren't referenced
+by <tt>setup.ini</tt>, and are thus are no longer installable, will be removed
+periodically.
+
+However, if you do need to remove a file from the distribution, upload an empty
+file with the name of the file that you want deleted, prefixed with a
+"<tt>-</tt>".
 
 <p>For example, if you want to delete the file <tt>foo-1.2-1.tar.xz</tt> then upload an empty file named:<pre> -foo-1.2-1.tar.xz</pre></p>
 
 <p>Note that files are not actually deleted; they are moved to a vault where they will be removed after some indeterminate amount of time.</p>
 
-<p>This technique should work with directories but some confusion may arise if you delete a directory, recreate it, and attempt to remove it again.  This scenario has not been tested.</p>
 <h2><a name="FAQ">Frequently Asked Questions</h2>
 
 <h3><a name="stalled">Q) Why aren't my files being transferred to the release area?  I've waited