http://bugzilla.suse.com/show_bug.cgi?id=977336
http://bugzilla.suse.com/show_bug.cgi?id=977336#c16
--- Comment #16 from Dr. Werner Fink ---
(In reply to Ludwig Nussel from comment #15)
Hmmm ... indeed I can split the spec into pieces and this generates at least
one new package ... nevertheless this looks more like a stupid restriction of
the build system, that is hard dependency rules without the possibility to make
a distinction/exception of what is required only by interactive used tools of a
package which is based on completion, and/or packages which requires only the
path/location of completion files them selfs.
Then the question rises if I should split off the devel spec file only or both
the devel and the doc spec files? IMHO the devel if enough but might lead to
more changes for packages not using `BuildRequire: pkgconfig(bash-completion)Ž
but plain `BuildRequire: bash-completionŽ. And there are also packages which
do require bash-completion for the their own interactive tools, that is the
file /usr/share/bash-completion/bash_completion or better the shell function
_init_completion() for their own completion files below
/usr/share/bash-completion/completions/
--
You are receiving this mail because:
You are on the CC list for the bug.