[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Solving the default-jdk-builddep mess


As some of you know, default-jdk-builddep (usually) pulls in two JDKs
(openjdk-6 and gcj/gij) to create -gcj packages.
  However, some people are not aware of this and looking at the name of
the package they assume it is the Java Team's "Default Build-Dependency"
or in other words the "Right Thing" (tm) to Depend on to get a java

I think the best idea is to rename default-jdk-builddep into something
else that does not trigger the "Ah, this is what I should put in
B-D"-instinct of our fellow maintainers and developers. If you have a
suggestion for a new name, please come with it.

Once we have found a new I suggest we clean up our own packages and bug
the few packages outside the Java Team that actually produces -gcj
packages before making default-jdk-builddep an alias of default-jdk.
  I think this will be easier than teaching the rest of Debian that
default-jdk-builddep should be default-jdk - particularly because this
mistake has found its way into the AM process[1], so currently new DDs
are taught this mistake is the "Right Thing" (tm).



Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: