Several issues

1) After applying update #6200 of config_perms module 6.x from 1.0 to 2.0-beta2, following error messages occur:
* warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home2/danstang/public_html/update.php on line 174.
* warning: Invalid argument supplied for foreach() in /home2/danstang/public_html/update.php on line 338.

2) If the module has been already installed and possibly uninstalled (in the past), then during installation the error appears stating that the table config_perms already exists in /{path}/includes/database.inc on line 555. In such case, records are ADDED to the table, even if those records are the same (except for the primary key). Apparently, uninstalling doesn't empty nor remove aforementioned table. It is Drupal's policy that uninstalling (NOT: disabling) modules should delete any data created by that module. NB: With the previous branch the table does not exist and with the current/ latest branch the table does exist.

3) As role management is integrated in Drupal core and to prevent confusion regarding security sensitive settings, please remove:
a) the 'administer site configuration' permission under the 'system module' in '{domain}/admin/user/permissions' and
b) following text in '{domain}/admin/settings/config_perms':
"Any role without 'administer site configuration' will be granted access to whatever permissions checked in the config_perms section of the permissions page. So in other words, if you want grant roles only a few of theses items, uncheck 'administer site configuration', check one or both of the display permissions, and check whatever you want them to have access to."

4) Adding a custom permission via '{domain}/admin/settings/config_perms' with:
a) name 'administer themes global settings' and path 'admin/build/themes/settings' and DISABLING that permission for a role via '{domain}/admin/user/permissions' does NOT PREVENT such role from accessing aforementioned path. NB: so, a path WITHOUT postfixed slash.
b) name 'administer theme specific settings' and path 'admin/build/themes/settings/' and ENABLING that permission for a role via '{domain}/admin/user/permissions' does NOT ALLOW such role from accessing aforementioned path. NB: so, a path WITH postfixed slash.
NB: 4a & 4b re-open following issue: http://drupal.org/node/760356

5) In '{domain}/admin/user/permissions', the 'display site building/ configuration menu' permission SHOULD cause that menu-item to appear, also when the 'access administration pages' permission is DISabled. It should do so without modifying access rights for any sub-items under aforementioned menu-item, obviously. The 'access administration pages' permission would be way too powerful for this.

Under '{domain}/admin/settings/config_perms':
6a) Include a link within the configuration instructions to '{domain}/admin/user/permissions'.
6b) Sort the table alphabetically by default, based on the 'Name' column (similar to '{domain}/admin/user/permissions').
6c) Change the checkbox "Delete" into buttons like the "Add" button per record, to prevent confusion.