I updated the PEAR-DB_Table to the current stable version 1.2.1, which works great. ebuild based upon PEAR-DB_Table-0.21.2-r1.ebuild, only added the dependency on PEAR-DB and updated version. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 69464 [details] PEAR-DB_Table-1.2.1.ebuild
PEAR-DB_Table-1.2.1 is in portage now.
hmmm You added HTML-QuickForm to the RDEPEND too, but it is an optional dependency. Doesn't seem necessary to me :)
I see no sense in introducing local USE flags for PEAR packages and their optional dependencies, sorry.
USE flags are indeed overkill, but in my opinion the user should take care of optional dependencies himself. I thought there were more PEAR ebuilds in portage that did not pull in optional packages, but when I start checking now, there seems to have been a policy change:) No problem, and thanks for the update :)
After a bit of playing around, I see what really happens. With an empty pear install, this is what I get when emerging PEAR-DB_Table: [ebuild N ] dev-php/PEAR-Date-1.4.3-r1 0 kB [ebuild N ] dev-php/PEAR-HTML_Template_Flexy-1.2.1-r1 -javascript 115 kB [ebuild N ] dev-php/PEAR-HTML_Template_IT-1.1-r1 18 kB [ebuild N ] dev-php/PEAR-HTML_Common-1.2.1-r1 3 kB [ebuild N ] dev-php/PEAR-HTML_QuickForm-3.2.5-r1 95 kB [ebuild N ] dev-php/PEAR-DB-1.7.6-r1 0 kB [ebuild N ] dev-php/PEAR-DB_Table-1.2.1 0 kB I think it is quite ridiculous :) When the user needs HTML_QuickForm, he will install it to get the functionality. By adding all the optional stuff as dependencies, a lot of junk gets pulled in. I think this is bad practice...
