Bug#1042855: openjdk-8: Please consider using libjpeg-dev virtual package as dependency

[Thorsten Glaser]

Vladimir Petko dixit:

>The attached patch updates control and rules to select libjpeg-dev as a

By the way, no need to patch rules for Ubuntu, just regenerate
debian/control is sufficient. I built the package for PPA with
that.

>I think I found the relevant quote:
>"To specify which of a set of real packages should be the default to
>satisfy a particular dependency on a virtual package, list the real
>package as an alternative before the virtual one." 7.5 Virtual
>Packages - Provides.

Yes, that was the one I was thinking of, and you’re right it
doesn’t apply here, as we don’t care which of them is used
(with the exception of the one we Depends on for dlopen).

The first paragraph of 7.5 makes it clear that we *can* use virtual
packages as B-D. However, virtual-package-names-list.yaml says:

# Packages MUST NOT use virtual package names (except privately, amongst
# a cooperating group of packages) unless they have been agreed upon and
# appear in this list.

And libjpeg-dev does not appear in this list.

>> +  bd_syslibs += libjpeg62-turbo-dev | libjpeg-dev,

| [1] While "Build-Depends", "Build-Depends-Indep" and "Build-Depends-
|     Arch" permit the use of alternative dependencies, those are only
|     used for the backports suite on the Debian autobuilders. On the
| […]
|     While this may limit the usefulness of alternatives in a single
|     release, they can still be used to provide flexibility in building
|     the same package across multiple distributions or releases, where

This indicates that specifically this was intended to make it
compatible with other distributions; if the other distribution
doesn’t accept alternatives, SOL…

bye,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool.”
						-- Edward Burr