r9997 - in /website: TODO subversion.pod

Thu Nov 29 14:45:57 UTC 2007

Author: jeremiah-guest
Date: Thu Nov 29 14:45:57 2007
New Revision: 9997

URL: http://svn.debian.org/wsvn/?sc=1&rev=9997
Log:
* some new content
* some small spelling changes

Modified:
    website/TODO
    website/subversion.pod

Modified: website/TODO
URL: http://svn.debian.org/wsvn/website/TODO?rev=9997&op=diff
==============================================================================

--- website/TODO (original)
+++ website/TODO Thu Nov 29 14:45:57 2007
@@ -14,7 +14,7 @@
 Debian Tags for our packages
 ============================
 
-Basically a reminder for myself, but whoever want to try it, please
+Basically a reminder for myself, but whoever wants to try it, please
 do:
 
 "Tag our packages."

Modified: website/subversion.pod
URL: http://svn.debian.org/wsvn/website/subversion.pod?rev=9997&op=diff
==============================================================================
--- website/subversion.pod (original)
+++ website/subversion.pod Thu Nov 29 14:45:57 2007
@@ -321,21 +321,22 @@
 
 =item UNRELEASED
 
-The package is work in progress. It is not uploaded yet and is not ready to be
-uploaded.
+When you put "UNRELEASED" in the release field, then this means the package is 
+work in progress. It is not uploaded yet and is not ready to be uploaded, it 
+still needs some work before it is in a state to be released.
 
 =item something else
 
 The package is either uploaded or is pending upload. The periodic cron job that
-generates L<http://pkg-perl.alioth.debian.org/qa/versions.html> distingueshes
+generates L<http://pkg-perl.alioth.debian.org/qa/versions.html> distinguishes
 between the two cases by looking in the package archive/incoming and NEW.
 
 =back
 
 Another thing to consider is adding C<DEBCHANGE_MULIMAINT=no> to
 C<~/.devscripts>. This avoids the [name] header in changelogs of packages that
-receive changes from several people, which is discouraged by current Group's
-policy.
+receive changes from several people, which is discouraged by current debian-perl
+group.
 
 =head1 8. Hints and Tricks
 
@@ -345,11 +346,11 @@
 
 One of the annoying things about B<svn-buildpackage> is that when you check out
 a package using the C<svn+ssh> protocol, it will ask your password pretty often
-when building, say 25 times.  This tends to get annoying by the second time you
-have to type in your password.  To avoid this, upload your public SSH key in
+when building, about 25 times. This tends to get annoying by the second time you
+have to type in your password. To avoid this, upload your public SSH key in
 the alioth account area (L<https://alioth.debian.org/account/editsshkeys.php>).
 
-Note that even if ssh-copy-id seem to work, this is only temporary since the
+Note that even if ssh-copy-id seems to work, this is only temporary since the
 authorized_keys file is re-generated from the alioth account info every now and
 then.
 
@@ -358,14 +359,15 @@
 
 =item How to not build directly under C<trunk/package/../build-area/>
 
-You might choose to check out all of C<trunk/>. When building from inside 
-such a checkout, the standard location for B<svn-buildpackage> will be
-C<trunk/package/../build-area/>.  This places the
-build area inside the SVN check-out directory, polluting the check-out.
+You might choose to check out all of C<trunk/>, this seems to be a common practice. 
+When building from inside the trunk directory, the standard location for 
+B<svn-buildpackage> will be C<trunk/package/../build-area/>. This places the
+build area inside the SVN check-out directory creating lots of files in the trunk
+directory which can get confusing since that directory is already quite large.
 
 The solution is to put one line in a file called C<trunk/package/.svn/deb-layout>.
 This file is automatically created by B<svn-buildpackage> but we can place our
-defaults there before it starts.  The line reads:
+defaults there before it starts. The line reads:
 
     buildArea=~/debian/perl/pkg-perl/build-area 
 


