Ainsi parlait Andrey Borzenkov :
> > Guillaume Rousse <[EMAIL PROTECTED]> 4.4-42mdk
> >
> > - added bash-completion
> > - spec cleanup
> > - bziped additional sources
>
> hey, if we start to ship completion functions with packages what about
> Zsh?
Well, i don't know if situation is the same.
bash is maintained independently from bash-completion project, wich is a
collection of shell function for completing common unix command. So
bash-completion is package separatly from bash itself first, from commands it
provide completion to also. It often turns into versioning nightmare: see how
different bash version are handled into bash-completion, for instance.
My own point is that commands that are mandrake specific (urpmi, rpmmon,
net-profile, etc...) are not supposed to be installed differently that from
mandrake packages, so it is better to ship them this way, so as to solve this
versioning issue first, than contribute them to distribution-independant
bash-completion project.
On the other hands, completion for other tools (lilo, freeciv, dsniff, to cite
a few from my own) are better handled at bash-completion project itself, so
as to be usable for other distributions also. In ideal world, they should
even get managed by upstream developpers.
How does that translate to zsh ?
BTW, feel free to use the cached package list (/var/lib/urpmi/names.*) fpons
implemented at my demand to speed up zsh completion also fro urpmi.
--
Murphy's Law will go into effect at the beginning of an evaluation.
-- Murphy's Laws of Teaching n°18
