Description: ------------ For package collectives, PHP5+, etc. we need a package tagging system and REST to match it

Additionally, there need to be a hierarchy of tag permissions tags that can be set by anyone tags that can only be set by PEAR Group/website admin This can be implemented with two tables CREATE TABLE tagnames ( tagid int not null auto_increment primary key, tagname varchar(50) not null, adminkey tinyint not null default 0, INDEX tagname_idx (tagname) ); CREATE TABLE tag_package_link ( package_id int not null, tagid int not null, PRIMARY KEY (package_id, tagid) ); Then, certain tags can be pre-entered as administrative tags such as "Website collective" "PEAR Installer collective" "PHP5" "PHP4" "Siberia" and so on

This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.