looks like the log4c author accepted ALL patches that made it's way into the log4c-1.0.11 ebuild and included them in his lates release... (I checked his CVS diffs) so a version bump is quite easy: take the 1.0.11 ebuild and just remove the src_unpack() section cause all those patches made it into the latest version Reproducible: Always Steps to Reproduce: 1. 2. 3.
Daniel, Please put yourself in the metadata.xml file as it seems you've become its maintainer
Thanks for the comprehensive bug report. version bump comited. Please tell me if there are any faults.
emerges just fine for me... just one final thing to note: could you take a look at the log4c-1.06 and log4c-1.06-r1 ebuild and change the HOMEPAGE for both cause this info is outdated and the site mentioned in there long dead. just use the same HOMEPAGE as for the recent ebuilds thx
Actually, 1.0.6 and 1.0.6-r1 should be removed from portage IMO because they both fail due to the access violations that I fixed in 1.0.11.