| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
| 1 | <!-- $NetBSD: submit.xml,v 1.23 2009/08/23 18:12:12 joerg Exp $ --> | | 1 | <!-- $NetBSD: submit.xml,v 1.24 2009/09/17 18:01:18 kano Exp $ --> |
| 2 | | | 2 | |
| 3 | <chapter id="submit"> <?dbhtml filename="submit.html"?> | | 3 | <chapter id="submit"> <?dbhtml filename="submit.html"?> |
| 4 | <title>Submitting and Committing</title> | | 4 | <title>Submitting and Committing</title> |
| 5 | | | 5 | |
| 6 | <sect1 id="submitting-binary-packages"> | | 6 | <sect1 id="submitting-binary-packages"> |
| 7 | <title>Submitting binary packages</title> | | 7 | <title>Submitting binary packages</title> |
| 8 | | | 8 | |
| 9 | <para>Our policy is that we accept binaries only from pkgsrc | | 9 | <para>Our policy is that we accept binaries only from pkgsrc |
| 10 | developers to guarantee that the packages don't contain any | | 10 | developers to guarantee that the packages don't contain any |
| 11 | trojan horses etc. This is not to annoy anyone but rather to | | 11 | trojan horses etc. This is not to annoy anyone but rather to |
| 12 | protect our users! You're still free to put up your home-made | | 12 | protect our users! You're still free to put up your home-made |
| 13 | binary packages and tell the world where to get them. NetBSD | | 13 | binary packages and tell the world where to get them. NetBSD |
| 14 | developers doing bulk builds and wanting to upload them please | | 14 | developers doing bulk builds and wanting to upload them please |
| @@ -78,27 +78,27 @@ | | | @@ -78,27 +78,27 @@ |
| 78 | and <varname>NETBSD_LOGIN_NAME</varname> variables. The general | | 78 | and <varname>NETBSD_LOGIN_NAME</varname> variables. The general |
| 79 | usage is to first make sure that your <filename>CHANGES-<replaceable>YYYY</replaceable></filename> | | 79 | usage is to first make sure that your <filename>CHANGES-<replaceable>YYYY</replaceable></filename> |
| 80 | file is up-to-date (to avoid having to resolve conflicts later-on) | | 80 | file is up-to-date (to avoid having to resolve conflicts later-on) |
| 81 | and then to <command>cd</command> to the package directory. For | | 81 | and then to <command>cd</command> to the package directory. For |
| 82 | package updates, <command>make changes-entry</command> is enough. | | 82 | package updates, <command>make changes-entry</command> is enough. |
| 83 | For new packages, or package moves or removals, set the | | 83 | For new packages, or package moves or removals, set the |
| 84 | <varname>CTYPE</varname> variable on the command line to "Added", | | 84 | <varname>CTYPE</varname> variable on the command line to "Added", |
| 85 | "Moved", or "Removed". You can set <varname>NETBSD_LOGIN_NAME</varname> | | 85 | "Moved", or "Removed". You can set <varname>NETBSD_LOGIN_NAME</varname> |
| 86 | in &mk.conf; if your local login name is | | 86 | in &mk.conf; if your local login name is |
| 87 | not the same as your NetBSD login name. The target also automatically | | 87 | not the same as your NetBSD login name. The target also automatically |
| 88 | removes possibly existing entries for the package in the | | 88 | removes possibly existing entries for the package in the |
| 89 | <filename>TODO</filename> file. Don't forget to commit | | 89 | <filename>TODO</filename> file. Don't forget to commit |
| 90 | the changes, e.g. by using <command>make changes-entry-commit</command>! | | 90 | the changes, e.g. by using <command>make changes-entry-commit</command>! |
| 91 | If you are not using a checkout directly from cvs.netbsd.org, but e.g. | | 91 | If you are not using a checkout directly from cvs.NetBSD.org, but e.g. |
| 92 | a local copy of the repository, you can set USE_NETBSD_REPO=yes. This | | 92 | a local copy of the repository, you can set USE_NETBSD_REPO=yes. This |
| 93 | makes the cvs commands use the main repository. | | 93 | makes the cvs commands use the main repository. |
| 94 | </para> | | 94 | </para> |
| 95 | </sect1> | | 95 | </sect1> |
| 96 | | | 96 | |
| 97 | <sect1 id="committing-importing"> | | 97 | <sect1 id="committing-importing"> |
| 98 | <title>Committing: Importing a package into CVS</title> | | 98 | <title>Committing: Importing a package into CVS</title> |
| 99 | <para>This section is only of interest for pkgsrc developers with write | | 99 | <para>This section is only of interest for pkgsrc developers with write |
| 100 | access to the pkgsrc repository. Please remember that cvs | | 100 | access to the pkgsrc repository. Please remember that cvs |
| 101 | imports files relative to the current working directory, and that | | 101 | imports files relative to the current working directory, and that |
| 102 | the pathname that you | | 102 | the pathname that you |
| 103 | give the <command>cvs import</command> command is so that it knows where | | 103 | give the <command>cvs import</command> command is so that it knows where |
| 104 | to place the files in the repository. Newly created packages should be | | 104 | to place the files in the repository. Newly created packages should be |