168988 2007-03-02 11:12 0000 dev-perl/XML-SAX: protect ParserDetails.ini 2007-03-04 15:59:51 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All Linux RESOLVED FIXED P2 normal --- 152198 1 Martin.vGagern@gmx.net perl@gentoo.org askwar@digitalprojects.com Martin.vGagern@gmx.net 2007-03-02 11:12:39 0000 dev-perl/XML-SAX installs a file called ParserDetails where installed parsers should be listed. One such other parser is XML-LibXML. Right now this file is a normal installed file and thus overwrites the version already present with each upgrade: # emerge XML-LibXML ... # grep . /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini [XML::SAX::PurePerl] http://xml.org/sax/features/namespaces = 1 [XML::LibXML::SAX::Parser] http://xml.org/sax/features/namespaces = 1 # emerge XML-SAX ... # grep . /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini [XML::SAX::PurePerl] http://xml.org/sax/features/namespaces = 1 I can see three solutions: 1. Handle ParserDetails.ini in postinst phase, like XML-LibXML does 2. Config-protect ParserDetails.ini 3. Have an eselect module take care of managing ParserDetails.ini The first approach is more automatic, but if I understand things correctly the default parser is derived from the order in this file, which it would break. We might introduce a new configuration file where users can specify thir precedence of parsers, and have every parser-related ebuild update the ini file according to that file. This could be based on an eclass or an eselect module. jakub@gentoo.org 2007-03-02 11:21:37 0000 eselect module?! You are joking, right? o_O Martin.vGagern@gmx.net 2007-03-02 11:32:25 0000 Created an attachment (id=111790) Patch to XML-SAX-0.15.ebuild moving ParserDetails.ini setting to postinst These modifications to the ebuild suppress the creation of ParserDetails.ini during the install phase completely. Instead a corresponding call is makde in postinst. The code there is taken from XML-LibXML but with an added "|| die". This approach will make the default parser setting dependant on emerge order, and as it is so far the ParserDetails.ini will still be around when you unmerge XML-SAX. I'm not sure what the right solution would be there. (In reply to comment #1) > eselect module?! You are joking, right? o_O I wasn't. Is eselect being deprecated, or is it simply not the right tool? mcummings@gentoo.org 2007-03-04 15:59:51 0000 applied, thanks! 111790 2007-03-02 11:32 0000 Patch to XML-SAX-0.15.ebuild moving ParserDetails.ini setting to postinst 168988.patch text/plain LS0tIC91c3IvcG9ydGFnZS9kZXYtcGVybC9YTUwtU0FYL1hNTC1TQVgtMC4xNS5lYnVpbGQJMjAw Ny0wMi0xNyAxNjozMzoyNS4wMDAwMDAwMDAgKzAxMDAKKysrIC91c3IvbG9jYWwvcG9ydGFnZS9k ZXYtcGVybC9YTUwtU0FYL1hNTC1TQVgtMC4xNS5lYnVpbGQJMjAwNy0wMy0wMiAxMTo1MjowOS4w MDAwMDAwMDAgKzAxMDAKQEAgLTI1LDggKzI1LDE4IEBACiAJZXZhbCAkKHBlcmwgJy1WOmluc3Rh bGx2ZW5kb3JsaWInKQogCXVucGFjayAke0F9CiAJY2QgIiR7U30iCisKKwkjIG5ldmVyIHdyaXRl IFBhcnNlckRldGFpbHMuaW5pIGluIGluc3RhbGw7IGRvIHRoYXQgaW4gcG9zdGluc3QKIAlzZWQg LWkgXAotCQktZSAicyxcKC1NWE1MOjpTQVhcKSwtSSR7RH0vJHtpbnN0YWxsdmVuZG9ybGlifSBc MSwiIFwKKwkJLWUgJ3MvaWYgKFwkd3JpdGVfaW5pX29rKS9pZiAoMCBcJlwmICR3cml0ZV9pbmlf b2spLycgXAogCQlNYWtlZmlsZS5QTCB8fCBkaWUKKwogCWVwYXRjaCAiJHtGSUxFU0RJUn0iL2Vu Y29kaW5ncy5wYXRjaAogfQorCitwa2dfcG9zdGluc3QoKSB7CisJcGVybC1tb2R1bGVfcGtnX3Bv c3RpbnN0CisJcGVybCAtTVhNTDo6U0FYIFwKKwkJLWUgIlhNTDo6U0FYLT5hZGRfcGFyc2VyKHEo WE1MOjpTQVg6OlB1cmVQZXJsKSktPnNhdmVfcGFyc2VycygpIiBcCisJCXx8IGRpZSAiZXJyb3Ig YWRkaW5nIHBhcnNlciIKK30K