Author: duncan
Date: 2005-03-23 15:44:32 -0500 (Wed, 23 Mar 2005)
New Revision: 42171
Modified:
trunk/release/packaging-howto
Log:
Fix typo
Modified: trunk/release/packaging-howto
===================================================================
--- trunk/release/packaging-howto 2005-03-23 20:44:04 UTC (rev 42170)
+++ trunk/release/packaging-howto 2005-03-23 20:44:32 UTC (rev 42171)
@@ -34,10 +34,11 @@
sure that it's building from the newly updated tarball, and not the
old one.
-3) Copy the resulting RPMs to a directory on NFS for deployment. In
- general, I put them in "/nfs/$USER/deploy/$RELEASE/$DISTRIBUTION/"
- in my NFS dir. $DISTRIBUTION should be the same as the name used by
- RC, this makes uploading the files much easier.
+3) Copy the resulting RPMs (in /tmp/$user/built-packages) to a
+ directory on NFS for deployment. In general, I put them in
+ "/nfs/$USER/deploy/$RELEASE/$DISTRIBUTION/" in my NFS
+ dir. $DISTRIBUTION should be the same as the name used by RC, this
+ makes uploading the files much easier.
Remember: DO NOT COPY SOURCE RPMS AND DEBUGINFO RPMS.
@@ -53,7 +54,7 @@
2) Apply the changes to the "src" directory.
-3) With the changed made, go back to the root module directory (parent
+3) With the changes made, go back to the root module directory (parent
of src and BUILD), and call "bb_regenerate <name of patch>".
4) A "foo.patch.new" will be created, read it and make sure it
@@ -67,4 +68,4 @@
<i>foo.patch-1</i>
</patch>
-6) Run "bb_redo" again, make sure the patch is applied.
\ No newline at end of file
+6) Run "bb_redo" again, make sure the patch is applied.
_______________________________________________
Mono-patches maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-patches
