There's been a lot of arguments on JPackage (http://www.jpackage.org/) list for
moving _javadocdir to a subdir of /usr/share/doc.
Since we share this macro definition with RedHat we'd like to know what your
opinion would be on this change.
Latest Jpackage rpm macros are available in the jpackage-utils macros that can
be downloaded at
some stuff is very raw, other is quite mature, comments are welcome.
The location for _javadocdir is configurable, easy enough
to change, very hard to guess what the default value should
So what is JPackage.org using for package dependencies? I've
been looking for Guinea pigs to drill a complete and reliable
set of java specific dependencies, but I know next to nothing
Any Java hackers out there?
Basically everyone agrees javadocs should share a single root since that makes
http exports easier. There's been a lot of arguments lately javadoc is pure
documentation and should move in a subdirectory of the general docdir.
If this is ok with you what def should we use ?
>So what is JPackage.org using for package dependencies?
We are very coarse grained in some aspects and very fine grained in others.
Usually dependency=jar name, with jar name build using aliases when several
implementations exist (we often need several implementations - we are vendor
agnostic, usually there are several free implementation and a single complete
non-free one. Most apps use the common alternative, apps that absoluteny need
the non free part depend on the proprietary implementation directly)
Anyway the easiest way to look at what we are doing is :
- look up the rpm/srpm repository at
- ask questions at JPackageemail@example.com
Everyone will be very happy to answer/help, we are trying to make life easier
for all rpm users (mainly RH/Mdk one) and a way to do it is work closely with
distributions when possible.
Was I clear enough or do your need more info ? I fear I was a bit laconic here:)
I guess this kind of problem can be treated outside of bugzilla now
that RedHat is involved into JPackage