[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/prep/maintain/html_node FTP-Upload-Directiv...
|
From: |
karl |
|
Subject: |
www/prep/maintain/html_node FTP-Upload-Directiv... |
|
Date: |
Mon, 07 Jan 2013 00:56:18 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: karl <karl> 13/01/07 00:56:18
Added files:
prep/maintain/html_node: FTP-Upload-Directive-File.html
FTP-Upload-Directory-Trees.html
FTP-Upload-File-Replacement.html
FTP-Upload-Release-File-Triplet.html
FTP-Upload-Standalone-Directives.html
Log message:
new nodes
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directive-File.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Directory-Trees.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-File-Replacement.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Release-File-Triplet.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/html_node/FTP-Upload-Standalone-Directives.html?cvsroot=www&rev=1.1
Patches:
Index: FTP-Upload-Directive-File.html
===================================================================
RCS file: FTP-Upload-Directive-File.html
diff -N FTP-Upload-Directive-File.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ FTP-Upload-Directive-File.html 7 Jan 2013 00:56:17 -0000 1.1
@@ -0,0 +1,165 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated January 6, 2013.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts. A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by Texinfo 4.13.93+dev, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Directive
File</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software:
FTP Upload Directive File">
+<meta name="keywords" content="Information for Maintainers of GNU Software:
FTP Upload Directive File">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2any">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up"
title="Automated FTP Uploads">
+<link href="FTP-Upload-Directory-Trees.html#FTP-Upload-Directory-Trees"
rel="next" title="FTP Upload Directory Trees">
+<link
href="FTP-Upload-Release-File-Triplet.html#FTP-Upload-Release-File-Triplet"
rel="previous" title="FTP Upload Release File Triplet">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="FTP-Upload-Directive-File"></a>
+<div class="header">
+<p>
+Next: <a href="FTP-Upload-Directory-Trees.html#FTP-Upload-Directory-Trees"
accesskey="n" rel="next">FTP Upload Directory Trees</a>, Previous: <a
href="FTP-Upload-Release-File-Triplet.html#FTP-Upload-Release-File-Triplet"
accesskey="p" rel="previous">FTP Upload Release File Triplet</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="FTP-Upload-Directive-File-1"></a>
+<h4 class="subsection">11.5.4 FTP Upload Directive File</h4>
+
+<a name="index-directive-file_002c-for-FTP-uploads"></a>
+
+<p>To repeat, a (signed) <em>directive file</em> must be part of every
+upload. The unsigned original is just a plain text file you can
+create with any text editor. Its name must be, e.g.,
+<samp>foo-1.0.tar.gz.directive</samp> for accompanying an upload of
+<samp>foo-1.0.tar.gz</samp>.
+</p>
+<p>After creating the file, run ‘<samp>gpg --clearsign
+foo-1.0.tar.gz.directive</samp>’, which will create
+<samp>foo-1.0.tar.gz.directive.asc</samp>; this is the file to be uploaded.
+</p>
+<p>When part of a triplet for uploading a release file, the directive
+file must always contain the directives <code>version</code>,
+<code>filename</code> and <code>directory</code>. In addition, a
<code>comment</code>
+directive is optional. These directives can be given in any order.
+</p>
+<p>Continuing our example of uploading <samp>foo-1.0.tar.gz</samp> for a
+package named <code>foo</code> to <code>ftp.gnu.org</code>, the values would
be as
+follows:
+</p>
+<dl compact="compact">
+<dt><code>version</code></dt>
+<dd><p>must be the value ‘<samp>1.2</samp>’ (the current version,
as of May 2012):<br>
+<tt>version: 1.2</tt>
+</p>
+</dd>
+<dt><code>filename</code></dt>
+<dd><p>must be the name of the file to be distributed:<br>
+<tt>filename: foo-1.0.tar.gz</tt>
+</p>
+</dd>
+<dt><code>directory</code></dt>
+<dd><p>specifies the final destination directory where the uploaded file and
+its <samp>.sig</samp> companion are to be placed. Here we will put our file
+in the top level directory of the package, as is the most common
+practice:<br>
+<tt>directory: foo</tt>
+</p>
+</dd>
+<dt><code>comment</code></dt>
+<dd><p>is optional, and ignored if present:<br>
+<tt>comment: let's hope this works!</tt>
+</p></dd>
+</dl>
+
+<p>Putting the above together, the complete contents of the directive
+file <samp>foo-1.0.tar.gz.directive</samp> for our example would be:
+</p>
+<div class="example">
+<pre class="example">version: 1.2
+directory: foo
+filename: foo-1.0.tar.gz
+comment: let's hope this works!
+</pre></div>
+
+<p>Then you ‘<samp>gpg --clearsign</samp>’ the file as given
above, and upload
+(using anonymous ftp) the three files:
+</p>
+<dl compact="compact">
+<dt><samp>foo-1.0.tar.gz</samp></dt>
+<dt><samp>foo-1.0.tar.gz.sig</samp></dt>
+<dt><samp>foo-1.0.tar.gz.directive</samp></dt>
+</dl>
+
+<p>to the host <samp>ftp-upload.gnu.org</samp>, directory
+<samp>/incoming/ftp</samp> (for official releases), or the directory
+<samp>/incoming/alpha</samp> (for test releases).
+</p>
+<p>After the system authenticates the signatures, the files
+<samp>foo-1.0.tar.gz</samp> and <samp>foo-1.0.tar.gz.sig</samp> are placed in
+the directory <samp>gnu/foo/</samp> on <code>ftp.gnu.org</code>. That is,
we’ll
+have made our release available at
+‘<code>http://ftp.gnu.org/gnu/foo/foo-1.0.tar.gz</code>’ (and then
from
+our many mirrors via
+‘<code>http://ftpmirror.gnu.org/foo/foo-1.0.tar.gz</code>’). Whew.
+</p>
+<p>A common reason for the upload not succeeding is your GPG signature
+not being registered with the upload system. There is nothing that
+makes this happen automatically. You must email the system
+administrators as described above (see <a
href="Automated-Upload-Registration.html#Automated-Upload-Registration">Automated
Upload Registration</a>).
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a href="FTP-Upload-Directory-Trees.html#FTP-Upload-Directory-Trees"
accesskey="n" rel="next">FTP Upload Directory Trees</a>, Previous: <a
href="FTP-Upload-Release-File-Triplet.html#FTP-Upload-Release-File-Triplet"
accesskey="p" rel="previous">FTP Upload Release File Triplet</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+
+
+
+</body>
+</html>
Index: FTP-Upload-Directory-Trees.html
===================================================================
RCS file: FTP-Upload-Directory-Trees.html
diff -N FTP-Upload-Directory-Trees.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ FTP-Upload-Directory-Trees.html 7 Jan 2013 00:56:17 -0000 1.1
@@ -0,0 +1,103 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated January 6, 2013.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts. A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by Texinfo 4.13.93+dev, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Directory
Trees</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software:
FTP Upload Directory Trees">
+<meta name="keywords" content="Information for Maintainers of GNU Software:
FTP Upload Directory Trees">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2any">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up"
title="Automated FTP Uploads">
+<link href="FTP-Upload-File-Replacement.html#FTP-Upload-File-Replacement"
rel="next" title="FTP Upload File Replacement">
+<link href="FTP-Upload-Directive-File.html#FTP-Upload-Directive-File"
rel="previous" title="FTP Upload Directive File">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="FTP-Upload-Directory-Trees"></a>
+<div class="header">
+<p>
+Next: <a href="FTP-Upload-File-Replacement.html#FTP-Upload-File-Replacement"
accesskey="n" rel="next">FTP Upload File Replacement</a>, Previous: <a
href="FTP-Upload-Directive-File.html#FTP-Upload-Directive-File" accesskey="p"
rel="previous">FTP Upload Directive File</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="FTP-Upload-Directory-Trees-1"></a>
+<h4 class="subsection">11.5.5 FTP Upload Directory Trees</h4>
+
+<a name="index-directory-trees_002c-in-ftp-uploads"></a>
+<a name="index-hierarchy_002c-under-ftp-upload-directory"></a>
+<a name="index-uploads_002c-directory-trees-in"></a>
+
+<p>You can make any directory hierarchy you like under your package
+directory. The system automatically creates any intermediate
+directories you specify in the <code>directory</code> directive.
+</p>
+<p>Slightly modifying the example above, the following directive file:
+</p>
+<div class="example">
+<pre class="example">version: 1.2
+directory: foo/foo-1.0
+filename: foo-1.0.tar.gz
+comment: creates per-version subdirectory as needed
+</pre></div>
+
+<p>would put the tar file in the <samp>foo-1.0/</samp> subdirectory of the
+package <code>foo</code>, thus ending up at
+‘<code>ftp.gnu.org:gnu/foo/foo-1.0/foo-1.0.tar.gz</code>’.
+</p>
+<p>However, to keep things simpler for users, we recommend not using
+subdirectories, unless perhaps each release of your package consists
+of many separate files.
+</p>
+
+
+
+
+</body>
+</html>
Index: FTP-Upload-File-Replacement.html
===================================================================
RCS file: FTP-Upload-File-Replacement.html
diff -N FTP-Upload-File-Replacement.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ FTP-Upload-File-Replacement.html 7 Jan 2013 00:56:17 -0000 1.1
@@ -0,0 +1,115 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated January 6, 2013.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts. A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by Texinfo 4.13.93+dev, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload File
Replacement</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software:
FTP Upload File Replacement">
+<meta name="keywords" content="Information for Maintainers of GNU Software:
FTP Upload File Replacement">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2any">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up"
title="Automated FTP Uploads">
+<link
href="FTP-Upload-Standalone-Directives.html#FTP-Upload-Standalone-Directives"
rel="next" title="FTP Upload Standalone Directives">
+<link href="FTP-Upload-Directory-Trees.html#FTP-Upload-Directory-Trees"
rel="previous" title="FTP Upload Directory Trees">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="FTP-Upload-File-Replacement"></a>
+<div class="header">
+<p>
+Next: <a
href="FTP-Upload-Standalone-Directives.html#FTP-Upload-Standalone-Directives"
accesskey="n" rel="next">FTP Upload Standalone Directives</a>, Previous: <a
href="FTP-Upload-Directory-Trees.html#FTP-Upload-Directory-Trees" accesskey="p"
rel="previous">FTP Upload Directory Trees</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="FTP-Upload-File-Replacement-1"></a>
+<h4 class="subsection">11.5.6 FTP Upload File Replacement</h4>
+
+<a name="index-replacing-uploaded-files"></a>
+<a name="index-uploads_002c-replacing"></a>
+
+<p>You can replace existing files that have already been uploaded by
+including a directive line <code>replace: true</code>. For example,
+you might like to provide a README file in the release directory and
+update it from time to time. The full directive file for that would
+look like this:
+</p>
+<div class="example">
+<pre class="example">replace: true
+version: 1.2
+directory: foo
+filename: README
+comment: replaces an existing README
+</pre></div>
+
+<p>It is ok if the file to be replaced doesn’t already exist; then the
+new file is simply added, i.e., the <samp>replace</samp> directive has no
+effect.
+</p>
+<p>When an existing file is replaced, the original is archived to a
+private location. There is no automated or public access to such
+archived files; if you want to retrieve or view them, please email
+<a href="mailto:address@hidden";>address@hidden</a>.
+</p>
+<p>We very strongly discourage replacing an actual software release file,
+such as <samp>foo-1.0.tar.gz</samp>. Releases should be unique, and
+forever. If you need to make fixes, make another release. If you
+have an exigent reason for a particular release file to no longer be
+available, it can be explicitly archived, as described in the next
+section.
+</p>
+<p>If you want to make the current release available under a generic
+name, such as <code>foo-latest.tar.gz</code>, that is better done with
+symlinks, also as described in the next section.
+</p>
+
+
+
+
+</body>
+</html>
Index: FTP-Upload-Release-File-Triplet.html
===================================================================
RCS file: FTP-Upload-Release-File-Triplet.html
diff -N FTP-Upload-Release-File-Triplet.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ FTP-Upload-Release-File-Triplet.html 7 Jan 2013 00:56:18 -0000
1.1
@@ -0,0 +1,103 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated January 6, 2013.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts. A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by Texinfo 4.13.93+dev, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Release File
Triplet</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software:
FTP Upload Release File Triplet">
+<meta name="keywords" content="Information for Maintainers of GNU Software:
FTP Upload Release File Triplet">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2any">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up"
title="Automated FTP Uploads">
+<link href="FTP-Upload-Directive-File.html#FTP-Upload-Directive-File"
rel="next" title="FTP Upload Directive File">
+<link href="Automated-Upload-Procedure.html#Automated-Upload-Procedure"
rel="previous" title="Automated Upload Procedure">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="FTP-Upload-Release-File-Triplet"></a>
+<div class="header">
+<p>
+Next: <a href="FTP-Upload-Directive-File.html#FTP-Upload-Directive-File"
accesskey="n" rel="next">FTP Upload Directive File</a>, Previous: <a
href="Automated-Upload-Procedure.html#Automated-Upload-Procedure" accesskey="p"
rel="previous">Automated Upload Procedure</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="FTP-Upload-Release-File-Triplet-1"></a>
+<h4 class="subsection">11.5.3 FTP Upload Release File Triplet</h4>
+
+<a name="index-FTP-uploads_002c-of-release-files"></a>
+
+<p>Ordinarily, the goal is to upload a new release of your package, let’s
+say, the source archive <samp>foo-1.0.tar.gz</samp>. To do this, you
+simultaneously upload three files:
+</p>
+<ol>
+<li> The file to be distributed; in our example, <samp>foo-1.0.tar.gz</samp>.
+
+</li><li> Detached GPG binary signature file for (1); for example,
+<samp>foo-1.0.tar.gz.sig</samp>. Make this with ‘<samp>gpg -b
foo-1.0.tar.gz</samp>’.
+
+</li><li> A clearsigned <em>directive file</em>; for example,
+<samp>foo-1.0.tar.gz.directive.asc</samp>, created with ‘<samp>gpg
+--clearsign foo-1.0.tar.gz.directive</samp>’. Its contents are
described in
+the next section.
+</li></ol>
+
+<p>The names of the files are important. The signature file must have
+the same name as the file to be distributed, with an additional
+<samp>.sig</samp> extension. The directive file must have the same name as
+the file to be distributed, with an additional <samp>.directive.asc</samp>
+extension. If you do not follow this naming convention, the upload
+<em>will not be processed</em>.
+</p>
+
+
+
+
+</body>
+</html>
Index: FTP-Upload-Standalone-Directives.html
===================================================================
RCS file: FTP-Upload-Standalone-Directives.html
diff -N FTP-Upload-Standalone-Directives.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ FTP-Upload-Standalone-Directives.html 7 Jan 2013 00:56:18 -0000
1.1
@@ -0,0 +1,167 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
+<html>
+<!-- Information for maintainers of GNU software, last updated January 6, 2013.
+
+Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
+2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
+2010, 2011, 2012, 2013 Free Software Foundation, Inc.
+
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
+Texts. A copy of the license is included in the section entitled
+"GNU Free Documentation License". -->
+<!-- Created by Texinfo 4.13.93+dev, http://www.gnu.org/software/texinfo/ -->
+<head>
+<title>Information for Maintainers of GNU Software: FTP Upload Standalone
Directives</title>
+
+<meta name="description" content="Information for Maintainers of GNU Software:
FTP Upload Standalone Directives">
+<meta name="keywords" content="Information for Maintainers of GNU Software:
FTP Upload Standalone Directives">
+<meta name="resource-type" content="document">
+<meta name="distribution" content="global">
+<meta name="Generator" content="texi2any">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link href="index.html#Top" rel="start" title="Top">
+<link href="Index.html#Index" rel="index" title="Index">
+<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
+<link href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" rel="up"
title="Automated FTP Uploads">
+<link
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
rel="next" title="FTP Upload Directive File - v1.1">
+<link href="FTP-Upload-File-Replacement.html#FTP-Upload-File-Replacement"
rel="previous" title="FTP Upload File Replacement">
+<style type="text/css">
+<!--
+a.summary-letter {text-decoration: none}
+blockquote.smallquotation {font-size: smaller}
+div.display {margin-left: 3.2em}
+div.example {margin-left: 3.2em}
+div.indentedblock {margin-left: 3.2em}
+div.lisp {margin-left: 3.2em}
+div.smalldisplay {margin-left: 3.2em}
+div.smallexample {margin-left: 3.2em}
+div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
+div.smalllisp {margin-left: 3.2em}
+kbd {font-style:oblique}
+pre.display {font-family: inherit}
+pre.format {font-family: inherit}
+pre.menu-comment {font-family: serif}
+pre.menu-preformatted {font-family: serif}
+pre.smalldisplay {font-family: inherit; font-size: smaller}
+pre.smallexample {font-size: smaller}
+pre.smallformat {font-family: inherit; font-size: smaller}
+pre.smalllisp {font-size: smaller}
+span.nocodebreak {white-space:nowrap}
+span.nolinebreak {white-space:nowrap}
+span.roman {font-family:serif; font-weight:normal}
+span.sansserif {font-family:sans-serif; font-weight:normal}
+ul.no-bullet {list-style: none}
+-->
+</style>
+
+
+</head>
+
+<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF"
vlink="#800080" alink="#FF0000">
+<a name="FTP-Upload-Standalone-Directives"></a>
+<div class="header">
+<p>
+Next: <a
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
accesskey="n" rel="next">FTP Upload Directive File - v1.1</a>, Previous: <a
href="FTP-Upload-File-Replacement.html#FTP-Upload-File-Replacement"
accesskey="p" rel="previous">FTP Upload File Replacement</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+<hr>
+<a name="FTP-Upload-Standalone-Directives-1"></a>
+<h4 class="subsection">11.5.7 FTP Upload Standalone Directives</h4>
+
+<a name="index-standalone-directives_002c-for-ftp-uploads"></a>
+<a name="index-directives-for-ftp-uploads_002c-standalone"></a>
+
+<p>The previous sections describe how to upload a file to be publicly
+released. It’s also possible to upload a directive file by itself to
+perform a few operations on the upload directory. The supported
+directives are:
+</p>
+<dl compact="compact">
+<dt><code>symlink</code></dt>
+<dd><p>creates a symlink.
+</p>
+</dd>
+<dt><code>rmsymlink</code></dt>
+<dd><p>removes a symlink.
+</p>
+</dd>
+<dt><code>archive</code></dt>
+<dd><p>takes a file or directory offline.
+</p></dd>
+</dl>
+
+<p>As for the directives described above, the <code>directory</code> and
+<code>version</code> directives are still required, the <code>comment</code>
+directive remains optional, and the <code>filename</code> directive is not
+allowed.
+</p>
+<p>When uploaded by itself, the name of the directive file is not
+important. But it must be still be signed, using ‘<samp>gpg
+--clearsign</samp>’; the resulting <samp>.asc</samp> file is what should
be
+uploaded.
+</p>
+<p>Here’s an example of the full directive file to create a
+<samp>foo-latest.tar.gz</samp> symlink:
+</p>
+<div class="example">
+<pre class="example">version: 1.2
+directory: foo
+symlink: foo-1.1.tar.gz foo-latest.tar.gz
+comment: create a symlink
+</pre></div>
+
+<p>If you include more than one directive in a standalone upload, the
+directives are executed in the sequence they are specified in. If a
+directive results in an error, further execution of the upload is
+aborted.
+</p>
+<p>Removing a symbolic link (with <code>rmsymlink</code>) which does not exist
+results in an error. On the other hand, attempting to create a
+symbolic link that already exists (with <code>symlink</code>) is not an
+error. In this case <code>symlink</code> behaves like the command
+<code>ln -s -f</code>: any existing symlink is removed before creating
+the link. (But an existing regular file or directory is not replaced.)
+</p>
+<p>Here’s an example of removing a symlink, e.g., if you decide not to
+maintain a <samp>foo-latest</samp> link any more:
+</p>
+<div class="example">
+<pre class="example">version: 1.2
+directory: foo
+rmsymlink: foo-latest.tar.gz
+comment: remove a symlink
+</pre></div>
+
+<p>And here’s an example of archiving a file, e.g., an unintended upload:
+</p>
+<div class="example">
+<pre class="example">version: 1.2
+directory: foo
+archive: foo-1.1x.tar.gz
+comment: archive an old file; it will not be
+comment: publicly available any more.
+</pre></div>
+
+<p>The <code>archive</code> directive causes the specified items to become
+inaccessible. This should only be used when it is actively bad for
+them to be available, e.g., you uploaded something by mistake.
+</p>
+<p>If all you want to do is reduce how much stuff is in your release
+directory, an alternative is to email <a
href="mailto:address@hidden";>address@hidden</a> and
+ask them to move old items to the <samp>http://ftp.gnu.org/old-gnu/</samp>
+directory; then they will still be available. In general, however, we
+recommend leaving all official releases in the main release directory.
+</p>
+
+<hr>
+<div class="header">
+<p>
+Next: <a
href="FTP-Upload-Directive-File-_002d-v1_002e1.html#FTP-Upload-Directive-File-_002d-v1_002e1"
accesskey="n" rel="next">FTP Upload Directive File - v1.1</a>, Previous: <a
href="FTP-Upload-File-Replacement.html#FTP-Upload-File-Replacement"
accesskey="p" rel="previous">FTP Upload File Replacement</a>, Up: <a
href="Automated-FTP-Uploads.html#Automated-FTP-Uploads" accesskey="u"
rel="up">Automated FTP Uploads</a> [<a href="index.html#SEC_Contents"
title="Table of contents" rel="contents">Contents</a>][<a
href="Index.html#Index" title="Index" rel="index">Index</a>]</p>
+</div>
+
+
+
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/prep/maintain/html_node FTP-Upload-Directiv...,
karl <=