Opened 7 years ago
Closed 6 years ago
#58217 closed enhancement (wontfix)
bash-completion: add subport for bash 3.2 compatible version
| Reported by: | mohd-akram (Mohamed Akram) | Owned by: | raimue (Rainer Müller) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | bash-completion |
Description
It would be nice to have a subport which supports the default macOS bash. I prefer to use the default bash to make sure scripts work on other systems. Homebrew currently does this by having two separate formulae, bash-completion & bash-completion@2. The last version compatible with bash 3.2 is bash-completion 1.3.
Change History (4)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
| Cc: | raimue removed |
|---|---|
| Owner: | set to raimue |
| Status: | new → assigned |
comment:2 Changed 7 years ago by raimue (Rainer Müller)
comment:3 Changed 7 years ago by mohd-akram (Mohamed Akram)
With Apple essentially deprecating bash in macOS Catalina, there won't be much need for this.
comment:4 Changed 6 years ago by raimue (Rainer Müller)
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.

As a side note, you can still test scripts with
/bin/bashregardless of the bash version you use as interactive shell. You are not forced to keep using bash 3.2 for this reason.bash-completion 1.3 is old and unmaintained. I see that it might be useful for some, therefore I am happy to apply a patch to provide a subport such as
bash-completion-legacyorbash32-completion. However, personally I see no point in providing ports without an upstream source that is actively working on bugfixes and improvements and will not work on this.