Some more insights for the README.

[cran2deb.git] / trunk / inst / doc / README

diff --git a/trunk/inst/doc/README b/trunk/inst/doc/README
index 45a7a4fe2a5c1edbdc81bcc0d9777c99b5fff30e..3609adfad960d119fd8f9a72ee5358572cb2e855 100644 (file)
--- a/trunk/inst/doc/README
+++ b/trunk/inst/doc/README
@@ -68,14 +68,15 @@ Create user "c2d" who shall have write permissions to the archive.
    This will also create the pbuilder environment if not already existing.
 
 7. manual changes - create a gpg key for your packages
+
        gpg --genkey
+
    and read through 'man gpg-agent' to set it up. Add that key to the
    pbuilder environment so the packages you signed and uploaded are 
    indeed acceptable to the distribution.
 
-       pbuilder --login \
-                --basetgz /var/cache/pbuilder/base-cran2deb-debian-amd64.tgz \
-                --save-after-login
+       sudo pbuilder  --login --save-after-login \
+            --basetgz /var/cache/pbuilder/base-cran2deb-debian-amd64.tgz
 
    Once logged in, in a separate shell perform as cran2deb user a
 
@@ -185,6 +186,31 @@ Create user "c2d" who shall have write permissions to the archive.
    for their own respective interpretation of a license's constraints
    and the effect on a redistribution of source and/or binary.
 
+11.Add licenses the way you think it is right. The script in 
+   'exec/repopulate' may offer ideas on how to mass-include what
+   you find in the svn. For new entries, you may prefer using
+   'cran2deb' license that expects to learn from from the command
+   line how to treat individual licenses:
+
+      $ cran2deb license accept akima
+      I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:21
+      N: adding akima accept? TRUE
+
+      $ cran2deb license hash_sha1 akima 485316717b03afbd6d20f7810f9123b4445c8660
+      I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:37
+      N: adding hash 485316717b03afbd6d20f7810f9123b4445c8660 for akima
+
+      $ cran2deb license ls
+      I: cran2deb svn: 344 building for debian-amd64 at 2011-02-11 18:46:53
+      accept akima 
+      hash_sha1 akima 485316717b03afbd6d20f7810f9123b4445c8660 
+
+   What happens here is that a license file was read and if that is
+   having the same hash value, then it is mapped to the license 'akima'.
+   The license 'akima' then again is told to be acceptable. It happened
+   here that the license is of the same name as the package that it 
+   occurs in.
+
 To think about
 
 1. After several updates of the repository, we have many outdated
@@ -209,6 +235,28 @@ To think about
                apt-cache search r-cran-$a
        done
 
+3. If running on a separate partition, the place reserved for cran2deb is not unlikely
+   to exceed your expectation, especially when also running BioConductor. You may
+   consider running cran2deb on logical volumes, like by LVM. Together with a file
+   system that allows its extension, the process is rather straight forward:
+
+       # lvextend -L+40G /dev/vg0/cran2deb 
+       Extending logical volume cran2deb to 115.04 GiB
+        Logical volume cran2deb successfully resized
+        # xfs_growfs /dev/vg0/cran2deb
+        meta-data=/dev/dm-6              isize=256    agcount=21, agsize=983040 blks
+                 =                       sectsz=512   attr=2
+        data     =                       bsize=4096   blocks=19671040, imaxpct=25
+                 =                       sunit=0      swidth=0 blks
+        naming   =version 2              bsize=4096   ascii-ci=0
+        log      =internal               bsize=4096   blocks=2560, version=2
+                 =                       sectsz=512   sunit=0 blks, lazy-count=1
+        realtime =none                   extsz=4096   blocks=0, rtextents=0
+        data blocks changed from 19671040 to 30156800
+
+   The directory does not even need to unmounted for that with XFS. 
+
+
 To debug:
 
 $ cran2deb help
@@ -230,5 +278,5 @@ database. It's a backup that can be versioned by SVN. There is a script called
 pull that, when run from the data directory will recreate all the files from
 the database EXCEPT for the licenses. The licenses cannot be recreated because
 licenses can be based on one-way hashes.  This process could certainly be
-improved.
+improved. But one gets the hang of it ater a while. So don't despair.