| 1 |
On 02/11/2011 06:38 PM, "Paweł Hajdan, Jr." wrote: |
| 2 |
> I'm not a member of QA team or libpng maintainer, but hopefully I'm not |
| 3 |
> going to write something horribly wrong here. |
| 4 |
> |
| 5 |
> To ensure good upgrade experience for our users, and learning some |
| 6 |
> lessons from previous, um... "disruptive" upgrade (1.2 -> 1.4), I'd have |
| 7 |
> some questions: |
| 8 |
> |
| 9 |
> 1) Are we going to have a tinderbox run *before* libpng-1.5 gets keyworded? |
| 10 |
|
| 11 |
Absolutely. |
| 12 |
|
| 13 |
> 4) What have we learned from libpng 1.2 -> 1.4 upgrade? I'd just like to |
| 14 |
> be better informed. |
| 15 |
|
| 16 |
One way under consideration: |
| 17 |
|
| 18 |
We have been discussing about removing libpng.pc, libpng.so and |
| 19 |
unversioned headers from the libpng 1.5.x package allowing it to install |
| 20 |
parallel with libpng 1.4.x. |
| 21 |
|
| 22 |
That means every package that has been checked working against 1.5.x, |
| 23 |
will need to be patched to link against -lpng15, use headers from the |
| 24 |
libpng15/ directory and use libpng15.pc instead. |
| 25 |
|
| 26 |
|
| 27 |
Or we go with the old route as with 1.2 to 1.4 but that means everything |
| 28 |
must be ported before it gets KEYWORDS. |
| 29 |
|
| 30 |
> Finally, it seems that hard work on --as-needed and automatic fixing of |
| 31 |
> .la files is going to make the upgrade experience better now, right? |
| 32 |
|
| 33 |
Indeed. That's a blessing :) |
Archives