{"id":443,"date":"2011-09-18T14:00:31","date_gmt":"2011-09-18T13:00:31","guid":{"rendered":"http:\/\/www.streppone.it\/cosimo\/blog\/2011\/09\/got-maintainership-of-bookmarksparser-and-gave-back-some-opera-love-to-it\/"},"modified":"2011-09-18T14:00:31","modified_gmt":"2011-09-18T13:00:31","slug":"got-maintainership-of-bookmarksparser-and-gave-back-some-opera-love-to-it","status":"publish","type":"post","link":"https:\/\/www.streppone.it\/cosimo\/blog\/2011\/09\/got-maintainership-of-bookmarksparser-and-gave-back-some-opera-love-to-it\/","title":{"rendered":"Got maintainership of Bookmarks::Parser, and gave back some Opera love to it"},"content":{"rendered":"

A new project just came in last week. We need to analyze Opera desktop builds (like this one<\/a>) and extract all settings from them and populate a nice database.<\/p>\n

We can do that quite easily since Opera stores most of its settings as either .ini<\/strong> or bookmarks (.adr)<\/strong> files.<\/p>\n

In Perl land, we can use Config::IniFiles<\/a> and Bookmarks::Parser<\/a> to do most of this. We had to subclass Config::IniFiles<\/code> to skip the non-standard Opera Preferences file ...<\/code> first line, while Bookmarks::Parser<\/code>, that includes an Opera-specific Bookmarks::Opera<\/code> class, wasn't updated with all the latest Opera-specific properties we use in our Desktop builds.<\/p>\n

Working on our first prototype of this build cataloger tool<\/strong>, we "patched" Bookmarks::Opera<\/code> to do what we needed, but the solution that makes the most long-term sense is to bring back some love upstream, so have our patches in the CPAN version of Bookmarks::Parser<\/code>. It's what makes the most sense to me anyway, so I usually always try to get in touch with the current author or maintainer.<\/p>\n

That's what I did in this case too, with great results. I was given co-maintainer bit in less than 24 hours. Rest of the story is in the github repository now<\/a>:<\/p>\n