[Bash-completion-devel] Dynamic completion loader.

[Ville Skyttä]

On 04/08/2011 11:02 AM, David Paleino wrote:

> However, being upstream, I can't just say "in Debian we have it, let's drop
> support altogether!". We somehow need to check how many users use 3.2 < x <
> 4.1.

We also need to be realistic - if there are no active
contributors/maintainers actively supporting and using our stuff let's
say with bash < 4.1, we shouldn't pretend it is actually supported and
let end users find out the problems for us, and we should be loud and
clear about that.

Even though I'm still very interested in bash completion that works with
bash 3.2 for now, there's always the 1.3 release which is fine for those
systems, and I don't particularly want anything but possibly occasional
bug fixes to that series.

So, given the answers so far, should we add a "drop bash < 4.1 support"
roadmap item, and already for 2.0 (my answer would be "yes", and +1)?  I
don't think we necessarily need to go wild and take advantage of
everything that 4.1+ would allow in 2.0, but we could start by cleaning
up cruft that is no longer required out of the way and introduce new
cool stuff in later 2.x releases if that can be done in a not too
disruptive way wrt. upgrading from previous 2.x releases.