On 19 Oct 2012 00:51, "Adam Williamson" <awilliam@xxxxxxxxxx> wrote:
>
> On Thu, 2012-10-18 at 16:43 +0200, Adam Tkac wrote:
> > On Thu, Oct 18, 2012 at 10:35:56AM -0400, Bill Nottingham wrote:
> > > Adam Tkac (atkac@xxxxxxxxxx) said:
> > > > I've just created
> > > > https://fedoraproject.org/wiki/Features/libjpeg-turbo-jpeg8-ABI page which
> > > > contains plan how to successfully move from current jpeg6 API/ABI to more recent
> > > > jpeg8 API/ABI for Fedora 19.
> > > >
> > > > All packages which depends on libjpeg.so will have to be rebuilt. Since I have
> > > > provenpackager privileges, I will cook some script which will rebuild all
> > > > pkgs automatically so no action will be required from maintainers.
> > > >
> > > > If there are no objections against this approach, I will start with this task
> > > > next week.
> > >
> > > Ouch. I can see a need for a compat library for some period of time here -
> > > the jpeg6 API has certainly been around for quite a long while.
> >
> > Hm, you are probably right. Since libjpeg is widely used, there might be some proprietary
> > apps which require it.
>
> Yeah, I'm with Bill. I note you listed this as the 'contingency plan'
> for the feature:
>
> Contingency Plan
>
> Create libjpeg-turbo-compat and libjpeg-turbo-compat-devel libraries
> with jpeg6 API/ABI and ship them in distro.
>
> I'd suggest you should just make it a plan from the start to have the
> -compat library available as part of the feature (so, really, just drop
> step 4 of 'scope'), and have the 'contingency plan' be 'abandon ship and
> go back to building with the jpeg6 API'.
You have to have the compat option to build everything as otherwise the build root breaks from the outset similar to what we saw with the recent libpng update to 1.5.
Peter
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
