This commit is contained in:
gferg 2000-07-13 16:57:45 +00:00
parent 9117ddc48b
commit 50f7f92699
5 changed files with 531 additions and 117 deletions

View File

@ -769,7 +769,7 @@ Netware, NT and Windows together. </Para>
IP-Masquerade-HOWTO</ULink>,
<CiteTitle>Linux IP Masquerade HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: May 2000</CiteTitle>.
<CiteTitle>Updated: July 2000</CiteTitle>.
How to enable the Linux IP Masquerade feature on a given Linux host. </Para>
</ListItem>
@ -851,6 +851,16 @@ Explains how to set up your server to allow CGI programs written in
Java and how to use Java to write CGI programs. </Para>
</ListItem>
<ListItem>
<Para>
<ULINK URL="../Java-Decompiler-HOWTO.html">
Java-Decompiler-HOWTO</ULink>,
<CiteTitle>Java Decompiler HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2000</CiteTitle>.
Will help you to de-compile the Java class programs. </Para>
</ListItem>
<ListItem>
<Para>
<ULINK URL="../JavaStation-HOWTO/index.html">
@ -1717,7 +1727,7 @@ an earlier implementation. </Para>
Software-Release-Practice-HOWTO</ULink>,
<CiteTitle>Software Release Practice HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: June 2000</CiteTitle>.
<CiteTitle>Updated: July 2000</CiteTitle>.
Describes good release practices for Linux open-source projects. </Para>
</ListItem>

View File

@ -116,7 +116,7 @@ Netware, NT and Windows together. </Para>
IP-Masquerade-HOWTO</ULink>,
<CiteTitle>Linux IP Masquerade HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: May 2000</CiteTitle>.
<CiteTitle>Updated: July 2000</CiteTitle>.
How to enable the Linux IP Masquerade feature on a given Linux host. </Para>
</ListItem>

View File

@ -148,6 +148,16 @@ Explains how to set up your server to allow CGI programs written in
Java and how to use Java to write CGI programs. </Para>
</ListItem>
<ListItem>
<Para>
<ULINK URL="../Java-Decompiler-HOWTO.html">
Java-Decompiler-HOWTO</ULink>,
<CiteTitle>Java Decompiler HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2000</CiteTitle>.
Will help you to de-compile the Java class programs. </Para>
</ListItem>
<ListItem>
<Para>
<ULINK URL="../mini/Kerneld/index.html">
@ -330,7 +340,7 @@ software distributions under Linux. </Para>
Software-Release-Practice-HOWTO</ULink>,
<CiteTitle>Software Release Practice HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: June 2000</CiteTitle>.
<CiteTitle>Updated: July 2000</CiteTitle>.
Describes good release practices for Linux open-source projects. </Para>
</ListItem>

File diff suppressed because it is too large Load Diff

View File

@ -9,7 +9,7 @@
<title>Software Release Practice HOWTO
<author>Eric S. Raymond &lt;esr@thyrsus.com&gt;
<date>2.3, 1 June 2000
<date>2.4, 12 July 2000
<abstract>
This HOWTO describes good release practices for Linux open-source projects.
@ -36,7 +36,7 @@ such as the World Wide Web.
This document will help you learn good practice. It is organized into
topic sections, each containing a series of checklist items. Think of
these as a pre-flight checklist for your distribution.
these as a pre-flight checklist for your software distribution.
<sect1>New versions of this document
<p>
@ -47,7 +47,7 @@ of Linux FTP sites, including <tt>metalab.unc.edu</tt> in
You can also view the latest version of this HOWTO on the World
Wide Web via the URL <url
url="http://metalab.unc.edu/LDP/HOWTO/Software-Release-Practice.html">.
url="http://www.linuxdoc.org/LDP/HOWTO/Software-Release-Practice.html">.
Feel free to mail any questions or comments about this HOWTO to
Eric S. Raymond, <url
@ -155,10 +155,14 @@ underscores. And don't capitalize or BiCapitalize without extremely
good reason -- it messes up the natural human-eyeball search order and
looks like some marketing weenie trying to be clever.
It confuses people when two different projects have the same stem name.
So try to check for collisions before your first release. A good place
to check is the <url url="http://metalab.unc.edu/pub/Linux" name="index
file of Metalab">.
It confuses people when two different projects have the same stem
name. So try to check for collisions before your first release. Two
good places to check are the <url
url="http://metalab.unc.edu/pub/Linux" name="index file of Metalab">
and the appindex at <url url="http://www.freshmeat.net"
name="Freshmeat">. Another good place to check is <url
name="SourceForge" url="http://www.sourceforge.net">; do a name search
there.
<sect>Good licensing and copyright practice: the theory
<p>
@ -302,10 +306,11 @@ For portability and stability, you should write either in ANSI C or a
scripting language that is guaranteed portable because it has just one
cross-platform implementation.
Scripting languages that qualify include Python, Perl, Tcl, and Emacs Lisp.
Plain old shell does <em>not</em> qualify; there are too many different
implementations with subtle idiosyncracies, and the shell environment
is subject to disruption by user customizations such as shell aliases.
Scripting languages that qualify include Python, Perl, Tcl, Emacs
Lisp, and PHP. Plain old shell does <em>not</em> qualify; there are
too many different implementations with subtle idiosyncracies, and the
shell environment is subject to disruption by user customizations such
as shell aliases.
Java holds promise as a portable language, but the Linux-available
implementations are still scratchy and poorly integrated with Linux.
@ -497,6 +502,15 @@ For extra style points, generate your spec file with a shellscript that
automatically plugs in the correct version number by analyzing the Makefile
or a version.h.
Note: if you suppy source RPMs, use BuildRoot to make the program be
built in /tmp or /var/tmp. If you don't, during the course of running
the make install part of your build, the install will install the
files in the real final places. This will happen even if there are
file collisions, and even if you didn't want to install the package at
all. When you're done, the files will have been installed and your
system's RPM database will not know about it. Such badly behaved
SRPMs are a minefield and should be eschewed.
<sect>Good communication practice
<p>
Your software won't do the world much good if nobody but you knows it
@ -585,7 +599,7 @@ url="http://www.tuxedo.org/~esr/writings/magic-cauldron/">.
These papers are not the last word on open-source development. But they
were the first serious analyses to be written, and have yet to be
superseded.
superseded (though the author hopes they will be somesday).
</article>