From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55566 invoked by alias); 11 May 2016 18:23:29 -0000 Mailing-List: contact cygwin-apps-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: cygwin-apps-cvs-owner@sourceware.org Received: (qmail 55527 invoked by uid 9795); 11 May 2016 18:23:28 -0000 Date: Wed, 11 May 2016 18:23:00 -0000 Message-ID: <20160511182328.55500.qmail@sourceware.org> From: jturney@sourceware.org To: cygwin-apps-cvs@sourceware.org Subject: [cygwin-apps htdocs - The cygwin-apps website files] branch master, updated. ce626d0b87fa14c76b7dd339b53f127002c35b9f X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: eeff75165d1ecec831c82c0584848210bf47ab14 X-Git-Newrev: ce626d0b87fa14c76b7dd339b53f127002c35b9f X-SW-Source: 2016-q2/txt/msg00016.txt.bz2 https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/apps-htdocs.git;h=ce626d0b87fa14c76b7dd339b53f127002c35b9f commit ce626d0b87fa14c76b7dd339b53f127002c35b9f Author: Jon Turney 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:

directory on cygwin.com will look like this:

-    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

Example using lftp to upload packages:

@@ -164,9 +164,10 @@ than this file in or under the given directory should be processed. The intent is that you create !ready when you have finished uploading everything that you plan on uploading.

-

Note: !ready files need to be created at least once for each -architecture that is uploaded, i.e., in each of the x86 and -x86_64 directories or in the package directories themselves.

+

Note: !ready files should not be created in the root of your +upload directory, i.e. they should be in the architecture +directories x86, x86_64 and noarch or in the package +directories themselves.

calm 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.

Removing files from the Cygwin distribution

-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 "-". +Removing files is not normally needed, as old versions which aren't referenced +by setup.ini, 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 +"-".

For example, if you want to delete the file foo-1.2-1.tar.xz then upload an empty file named:

 -foo-1.2-1.tar.xz

Note that files are not actually deleted; they are moved to a vault where they will be removed after some indeterminate amount of time.

-

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.

Frequently Asked Questions

Q) Why aren't my files being transferred to the release area? I've waited