Hi Niels, 2013/5/17 Niels Thykier <ni...@thykier.net>
> On 2013-05-17 22:31, Damien Raude-Morvan wrote: > >> Emmanuel Bourg <ebo...@apache.org> > >> There are three packages implementing the Java Activation Framework in > >> Debian. They could be removed now that Java 6 and upward integrate the > >> most recent version of JAF. > >> > > > > Even if default-jdk package will soon become alias for openjdk-7 [1], for > > now it's a mix of openjdk-6 on some platform and GCJ (vaguely Java 5 > > compliant) on others. > > > > It means that if someone try to build a package which use JAF (and so > > Build-Depends only on "default-jdk") it will fail on platform using GCJ. > > For this kind of needs, I think we could use a versionned Build-Depends > on > > "default-jdk (>= 1:1.6)". > > > > The version of default-* packages are NOT useful for specifying a Major > java version. In particularly, on some architectures it has a version > 2:1.5 (i.e. >> 1:1.6, but using Java5). I suspect this can happen again > if we ever need to back out of a default change again. > I've check on [1] and [2] before coming back here with this idea. I just re-checked again and I can't found any arch with a "2:1.5" epoch version. Am I missing something obvious ? > If we want to use default-jdk in that way (i.e. let it have a version > that is useful for determining the Java major version), we need to have > a policy for dealing with """What happens if we need to "downgrade" > default-jdk from X to X-1?""". > You're right, this kind of requalification of default Java runtime for one or more arch already happenned in the past (hence our curent "1" epoch number). I'm just looking for a solution to Build-Depends on the right JDK 1/ without a specific dependency on openjdk-6 and openjdk-7 (impl) 2/ with a clear way to declare that we depends a specific J2SE API level [1] http://packages.debian.org/fr/experimental/default-jdk [2] http://packages.debian.org/fr/sid/default-jdk -- Damien
