Hi Would it be possible to create a blank ParserDetails.ini file earlier in the ebuild that could then be updated in the post install step? Having it tracked by portage would mean when upgrading perl versions it wouldn't be left behind in /usr/lib64/perl5/ Thanks
Unfortunately it doesn't really work that way. That file is generated by *multiple* packages, and thus, providing it in the ebuild itself would create a file collision. I have plans to have a sort of package all the packages that *could* update this file would depend on, and *that* package would provide parserdetails.ini, but there's additional work that needs to take place for that to happen, including having some smarter mechanism for setting it up other than "whatever was installed last does something"
*** This bug has been marked as a duplicate of bug 456938 ***