Am Sonntag, 25. August 2013, 01:02:21 schrieb Michael Schwendt:
Can we please enhance the packaging guidelines and request packagers to
add comments to explicit Requires more often than not?
Explicit Requires on package names are fragile. The contents of the
required package may move to a different (sub)package.
Especially in case of scripting languages, rpm is unable to find the runtime
deps automatically in almost all cases. So we have to add them anyway. Well,
if the extra dep provides extra features which are not needed for the basic
functionality of the software, then we should move this to a subpackage which
pulls the extra dep and keep it off the main package. This would help to reduce
the deps, and users can decide what they really need.
Uncommented Requires don't give a hint about why they have been
what inside a package is needed (with obvious exceptions, such as one
Python based package requiring another Python based package). What inside
a package is required? An executable? A directory? A datadir? A DBus
If rpm adds its requirements due to library calls, it even doesn't comment
this ;) But I agree with you, it would be helpful to have some explanation
what a dependency is for. In most cases we can consult the docs in the tarball
or the project homepage, but sometimes the packager stumbles upon a missing
dep during the tests. At least in that case, the dep should be commented.