+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.
+