New and simplified organisation of backporting scripts

Now backports for different distributions (squeeze, wheezy, jessie) can be
started from the same working directory. Also, single package builds
can be done without editing a script.



git-svn-id: svn+ssh://stiller/home/schatz/reps/r-backports@111 f247ebf9-aa24-0410-a698-f940e971ad2b

1 files changed, 16 insertions, 4 deletions

diff --git a/README b/README
index f280923..13fc280 100644
--- a/README
+++ b/README
@@ -22,9 +22,19 @@ This means I have the appropriate aptcache and buildresult directories set up
 under /var/cache/pbuilder. I have several pbuilder images used for package
 creation under /var/cache/pbuilder, among others:
 
-/var/cache/pbuilder/squeeze-i386-base.tgz
+  /var/cache/pbuilder/squeeze-i386-base.tgz
 
-These have a standard Debian mirror, the security sources and the Debian
+With the pbuilderrc mentioned above, this can be created as a normal user with
+
+  export ARCH=i386
+  export DIST=squeeze
+  sudo -E pbuilder create
+
+Then, using
+
+  sudo -E pbuilder login --save-after-login
+
+these have a standard Debian mirror, the security sources and the Debian
 backports repository setup in their /etc/apt/sources.list, as well as my local
 http package source where the r-base package build results are available. I
 have also imported the apt key of my repository inside the pbuilder chroots.
@@ -35,5 +45,7 @@ For some reason, the keyring option to debootstrap is not used (necessary on
 Ubuntu) so I need to pass this on the commandline when building the pbuilder
 chroot for wheezy-i386.
 
-When using these scripts on Debian, I configure sudo to allow my normal user to
-use pbuilder, apt-get and the backporting scripts
+When using these scripts on Debian, I used to configure sudo to allow my normal
+user to use pbuilder, apt-get and the backporting scripts. Currently, I have 
+set up my wheezy installation using the Ubuntu like sudo configuration that
+can be selected during installation.