On Wednesday 04 August 2010, seth vidal wrote: > On Wed, 2010-08-04 at 18:51 +0000, Ville Skyttä wrote: > > repoquery.py | 2 +- > > > > yum-utils.bash | 29 +++++++++++++++++++++++------ > > 2 files changed, 24 insertions(+), 7 deletions(-) > > > > New commits: > > commit 36757075f0954cdcc13216186337c96c27083929 > > Author: Ville Skyttä <ville.sky...@iki.fi> > > Date: Wed Aug 4 21:51:13 2010 +0300 > > > > Add repoquery --lookaside bash completion. > > Is there a bash_completion parser for optparser so that you don't have > to do these all the time?
Upstream bash-completion does have a few helpers that try to grab (long) options from --help output. It's better than nothing, but it has obviously no way of knowing what options a long option might take (for example --lookaside needs a repo id) and it covers only long options (so non-option arguments would not be covered) so some manual maintenance would be required anyway. And using that stuff would mean introducing a dependency on upstream bash- completion or shipping a copy of those helpers. It's no problem for me to update/maintain the completion files, nor do I think it's such a big deal if some newly added options fall through the cracks in some releases if I don't manage to update stuff in time. Dropping a note to me or on list a few days before intended yum/yum-utils/createrepo release dates would help with that... _______________________________________________ Yum-devel mailing list Yum-devel@lists.baseurl.org http://lists.baseurl.org/mailman/listinfo/yum-devel
