I'm not a member of QA team or libpng maintainer, but hopefully I'm not going to write something horribly wrong here.
To ensure good upgrade experience for our users, and learning some lessons from previous, um... "disruptive" upgrade (1.2 -> 1.4), I'd have some questions: 1) Are we going to have a tinderbox run *before* libpng-1.5 gets keyworded? 2) If the upgrade is non-trivial, i.e. just emerge -uDNa world and revdep-rebuild isn't going to fix it, will we have an upgrade guide, possibly as a news item? 3) Can we do something to make catching libpng problems easier? As Samuli pointed out in https://bugs.gentoo.org/show_bug.cgi?id=354479 there is a predictable compilation warning. How about making portage print it as a QA warning, so more people can report the issues without even emerging libpng-1.5 on their systems? That may be a good backup option for the tinderbox too. 4) What have we learned from libpng 1.2 -> 1.4 upgrade? I'd just like to be better informed. Finally, it seems that hard work on --as-needed and automatic fixing of .la files is going to make the upgrade experience better now, right? Paweł Hajdan, Jr. P.S. The 1.2 -> 1.4 upgrade wasn't really bad for me, but I guess it could be frustrating for some people, and I just wonder if we can make it better.
signature.asc
Description: OpenPGP digital signature
