Bug#814866: racket: bogus recommends: libjpeg8, libpng12-0

[Adam Borowski]

On Tue, Feb 16, 2016 at 09:37:35AM -0400, David Bremner wrote:
> Adam Borowski  writes:
> > racket has a bunch of hard-coded recommends: that go out of sync with what
> > it's built against.
> 
> The recommends are (more or less) needed because racket dlopens a bunch
> of things, which is not detected by the usual machinery. That doesn't
> excuse them being out of sync, of course. Better ideas for how to manage
> this are welcome.

I see.  It is possible to do so in an automated way, but that would require
some work.  This might possibly not save labour over doing this by hand.

If things are to remain a manual whack-a-mole, please consider this bug
report a notification that the libjpeg8 dependency is bogus since pre-jessie
and libpng12 will become bogus very soon.

-- 
A tit a day keeps the vet away.

Bug#814866: racket: bogus recommends: libjpeg8, libpng12-0

[David Bremner]

Adam Borowski  writes:

> Package: racket
> Version: 6.3-3
> Severity: normal
>
>
> racket has a bunch of hard-coded recommends: that go out of sync with what
> it's built against.

The recommends are (more or less) needed because racket dlopens a bunch
of things, which is not detected by the usual machinery. That doesn't
excuse them being out of sync, of course. Better ideas for how to manage
this are welcome.

Bug#814866: racket: bogus recommends: libjpeg8, libpng12-0

[Adam Borowski]

Package: racket
Version: 6.3-3
Severity: normal


racket has a bunch of hard-coded recommends: that go out of sync with what
it's built against.

It has build-dependency on libjpeg-dev which, in jessie and unstable, is
libjpeg62-turbo.

libpng12-0 is currently valid but will become bad in a few days when the
png16 transition starts.