cvs: peardoc /en/guide/developers release.xml

davey Fri May 2 07:37:38 2003 EDT Modified files: /peardoc/en/guide/developers release.xml Log: 'Changed packaging the release tarball notes to show that appending package.xml is optional for the pear package command.' Index: peardoc/en/guide/developers/release.xml diff -u peardoc/en/guide/developers/release.xml:1.3 peardoc/en/guide/developers/release.xml:1.4 --- peardoc/en/guide/developers/release.xml:1.3 Fri May 2 07:27:59 2003 +++ peardoc/en/guide/developers/release.xml Fri May 2 07:37:37 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.3 $ --> +<!-- $Revision: 1.4 $ --> <chapter id="developers.release"> <docinfo> @@ -59,10 +59,17 @@ <para> Now that your package has a valid package definition file, you can package the release tarball. Cd to the top-level directory of the package and run: - <command>pear package package.xml</command>. This will create the release - tarball (gzipped if zlib support is present) that will be used later to - upload the new release. + <command>pear package &lt;package definition XML file&gt;</command> + This will create the release tarball (gzipped if zlib support is present) + that will be used later to upload the new release. </para> + + <note> + <para> + If your package defintion XML file is called package.xml you do not need + to append it to the <command>pear package</command> command. + </para> + </note> <para> Next, you should install the package locally by running: <command>pear