On Wed, May 22, 2013 at 4:05 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
On Wed, May 22, 2013 at 09:39:06 +0100,
Peter Robinson <pbrobinson(a)gmail.com> wrote:
>
> On Fri, May 17, 2013 at 12:17 PM, Kalev Lember <kalevlember(a)gmail.com>
> wrote:
>
> The way it was done last time on the 1.5 upgrade was to have a
> compat-libpng package that had the 1.5 release so that nothing broke
> while things were rebuilt and then once the vast majority of the
> rebuild happened it was then dropped to avoid this problem.
The last time a lot of packages needed patches to use 1.5. So it was
expected to take a while to clean up all of the packages that used 1.2. I
get the impression, that this time around simple rebuilds are expected to
work in most cases.
The problem is that a lot of the core packages in the build root
depend on libpng so you can't bump the soname without having the
compat one around because you can't rebuild a whole bunch of packages
that need to be installed to rebuild them so you end up in a chicken
and egg senario.... bump libpng soname ...... can't install build
chain to rebuild other packages because a required soname dependency
has disappeared :-)
Peter