Ville Skyttä a écrit :
For the last issue, which is to distribute in a single package, and
activate only when needed, I initially attempted to use triggers too.
However, we now have 175 various completions in contrib directories,
meaning 175 * 2 triggers (installation/uninstallation) to maintain,
keeping track of the various mismatch between package names and
completion file name. All in all, that's just impossible.
This is surely a bit (yep, a bit, not a lot) of work, but why would it be
impossible? I haven't packaged post 1.0 bash-completion for Fedora but I do
for now intend to continue with the trigger approach. With a few helper
macros I think it's quite manageable, see
http://cvs.fedoraproject.org/viewvc/rpms/bash-completion/devel/bash-
completion.spec?revision=1.42&view=markup
Interesting. Maybe a bit of lua scripting could help also here.
--
BOFH excuse #319:
Your computer hasn't been returning all the bits it gets from the Internet.
_______________________________________________
Bash-completion-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
