On 02/11/2011 06:38 PM, "Paweł Hajdan, Jr." wrote: > 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?
Absolutely. > 4) What have we learned from libpng 1.2 -> 1.4 upgrade? I'd just like to > be better informed. One way under consideration: We have been discussing about removing libpng.pc, libpng.so and unversioned headers from the libpng 1.5.x package allowing it to install parallel with libpng 1.4.x. That means every package that has been checked working against 1.5.x, will need to be patched to link against -lpng15, use headers from the libpng15/ directory and use libpng15.pc instead. Or we go with the old route as with 1.2 to 1.4 but that means everything must be ported before it gets KEYWORDS. > 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? Indeed. That's a blessing :)
