It seems one interesting question about Java guidelines has no answer yet...
Orcan Ogetbil wrote:
Conrad Meyer wrote:
> Orcan Ogetbil wrote:
>> JAVA GUIDELINES:
>> - BuildRequires: jpackage-utils
>> Why do we need this? I understand Requires: jpackage-utils for
>> directory ownership etc, but the BR is not necessary for most
>> packages (at least all the ones I saw so far). I think this should
>> *not* be required.
> rpm -ql jpackage-utils | grep /usr/bin
> A lot of these are useful.
Yes, I agree. But can't we leave the BR out for those packages which don't use
AFAIK minimization of dependencies between components is an important
development target of any system.
Establishing of the superfluous dependencies is not a good development
approach even if we'll add a dependency on a component that is very
useful in all other cases.
The jemmy package  is an example where dependencies on the
jpackage-utils are redundant.
Are there any valuable reasons for establishing dependencies on the
jpackage-utils if such facilities are not used in a package/subpackage?
Thanks in advance,