#51348: bash-completion @2.1: update to 2.3 ------------------------------+---------------------- Reporter: xeron.oskom@… | Owner: raimue@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: bash-completion | ------------------------------+---------------------- Comment (by raimue@…): Replying to [comment:3 xeron.oskom@…]:
* Release tarballs are preferred over tarballs generated by GitHub
If release tarballs are preferred why don't we set `github.tarball_from releases` by default? I actually didn't know about `github.tarball_from` parameter and it wasn't working w/o `v` after version so I just put it there :)
Release tarballs are attached manually to a release (usually what `make dist` produces for automake-based build systems). Not all projects release such tarballs, so the default is what works for every project. The default for the github port group fetches a tarball that is generated by GitHub from version control, which does not include the configure scripts, automake helpers, m4 macros, etc.
* Retain bash-completion-devel for the time being until it is properly marked as replaced_by and then removed
We should probably do this since `bash-completion-devel` is somehow useless right now.
Agreed, I will look into that. -- Ticket URL: <https://trac.macports.org/ticket/51348#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X