[Piuparts-commits] rev 157 - in trunk: . debian

[Holger Levsen]

Author: holger
Date: 2008-05-11 19:24:30 +0000 (Sun, 11 May 2008)
New Revision: 157

Modified:
   trunk/debian/changelog
   trunk/how-to-use-piuparts.txt
Log:
re-add removed tips

Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog	2008-05-11 19:16:29 UTC (rev 156)
+++ trunk/debian/changelog	2008-05-11 19:24:30 UTC (rev 157)
@@ -8,8 +8,7 @@
   * Added a --debfoster-options option, to allow the user to override
     debfoster's default options and test with more packages installed
     in the chroot. (Closes: #458922)
-  * Doc fix: remove mention of pbuilder in how-to-use-piuparts.txt.
-    Using -s to save the tarball is easier.
+  * Mention piuparts -s in in how-to-use-piuparts.txt.
   * Finally fixes the check for broken symlinks. Thanks go to
     Tobias Grimm for the patch. Closes: #468157, 478587.
   * Ignore /var/cache/ldconfig/aux-cache.
@@ -19,7 +18,7 @@
   * Added -w to lsof call to suppress warnings. (Closes: #466102).
 
   [ Lucas Nussbaum ]
-  * Keep /proc mounted. Switch to calling tar directly in 
+  * Keep /proc mounted. Switch to calling tar directly in
     pack_into_tgz(). Minor refactorings. Thanks go to Tobias Grimm
     for the patch. Closes: #478577.
   * Move piuparts to priority: extra, since it depends on debootstrap which
@@ -29,7 +28,7 @@
   * Add a copyright statement to debian/copyright.
   * Add support for post_upgrade custom script.
 
- -- Lucas Nussbaum <lucas at lucas-nussbaum.net>  Mon, 05 May 2008 13:01:01 +0200
+ -- Holger Levsen <holger at debian.org>  Sun, 11 May 2008 21:20:37 +0200
 
 piuparts (0.30) unstable; urgency=low
 

Modified: trunk/how-to-use-piuparts.txt
===================================================================
--- trunk/how-to-use-piuparts.txt	2008-05-11 19:16:29 UTC (rev 156)
+++ trunk/how-to-use-piuparts.txt	2008-05-11 19:24:30 UTC (rev 157)
@@ -32,7 +32,26 @@
 time takes too much time, even if you are using a local mirror or a caching tool 
 such as approx. 
 
-Piuparts has the option of using a tarball as the contents of the initial
+Piuparts has the option of using a tarball as the contents of the initial chroot, 
+instead of building a new one with debootstrap. A easy way to use this option 
+is use a tarbal created with pbuilder. If you are not a pbuilder user, you can 
+create this tarball with the command (again, as root):
+
+    # puilder create
+ 
+then you only have to remember to update this tarball with:
+
+    #  pbuilder update.
+
+To run piuparts using this tarball:
+
+    # piuparts -p sm_0.6-1_i386.deb
+
+If you want to use your own pre-made tarball:
+
+    # piuparts --basetgz=/path/to/my/tarball.tgz sm_0.6-1_i386.deb
+
+Piuparts also has the option of using a tarball as the contents of the initial
 chroot, instead of building a new one with debootstrap. You can save a tarball
 for later use with the -s (--save) piuparts option.