[csw-devel] SF.net SVN: gar:[16775] csw/mgar/gar/v2/lib/python/csw_upload_pkg.py

wahwah at users.sourceforge.net wahwah at users.sourceforge.net
Mon Jan 16 12:48:43 CET 2012


Revision: 16775
          http://gar.svn.sourceforge.net/gar/?rev=16775&view=rev
Author:   wahwah
Date:     2012-01-16 11:48:43 +0000 (Mon, 16 Jan 2012)
Log Message:
-----------
csw-upload-pkg: --remove information

Add more information specific to the --remove option.

Modified Paths:
--------------
    csw/mgar/gar/v2/lib/python/csw_upload_pkg.py

Modified: csw/mgar/gar/v2/lib/python/csw_upload_pkg.py
===================================================================
--- csw/mgar/gar/v2/lib/python/csw_upload_pkg.py	2012-01-16 10:26:21 UTC (rev 16774)
+++ csw/mgar/gar/v2/lib/python/csw_upload_pkg.py	2012-01-16 11:48:43 UTC (rev 16775)
@@ -27,23 +27,33 @@
 BASE_URL = "http://buildfarm.opencsw.org"
 RELEASES_APP = "/releases"
 DEFAULT_CATREL = "unstable"
-USAGE = """%prog [ options ] <pkg1> [ <pkg2> [ ... ] ]
+USAGE = """%prog [ options ] <file1.pkg.gz> [ <file2.pkg.gz> [ ... ] ]
 
 Uploads a set of packages to the unstable catalog in opencsw-future.
 
-- When an ARCH=all package is sent, it's added to both sparc and i386 catalogs
+- When an architecture-independent package is uploaded, it gets added to both
+	sparc and i386 catalogs
+
 - When a SunOS5.x package is sent, it's added to catalogs SunOS5.x,
   SunOS5.(x+1), up to SunOS5.11, but only if there are no packages specific to
   5.10 (and/or 5.11).
-- If a package update is sent, the tool uses catalogname to identify the
-  package it's supposed to replace
 
-The --remove option affects the same catalogs as the regular use, except that
-it removes assignments of a given package to catalogs, instead of adding them.
+- If a package update is sent, the tool uses both the catalogname and the
+	pkgname to identify the package it's updating. For example, you might upload
+	foo_stub/CSWfoo and mean to replace foo/CSWfoo with it.
 
 The --os-release flag makes %prog only insert the package to catalog with the
 given OS release.
 
+= Removing packages from the catalog =
+
+The --remove option works the same way as the regular use, except that it
+removes assignments of a given package to catalogs, instead of adding them.
+
+When removing packages from catalogs, files on disk are passed as arguments.
+On the buildfarm, all files are available under the /home/mirror/opencsw
+directory.
+
 For more information, see:
 http://wiki.opencsw.org/automated-release-process#toc0
 """

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.



More information about the devel mailing list