Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#51348 closed update (fixed)

bash-completion @2.1: update to 2.3

Reported by: xeron (Ivan Larionov) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc:
Port: bash-completion

Description

bash-completion project has been moved to https://github.com/scop/bash-completion

There's a new version 2.3.

Patch attached.

Attachments (1)

bash-completion.patch (13.4 KB) - added by xeron (Ivan Larionov) 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by xeron (Ivan Larionov)

Attachment: bash-completion.patch added

comment:1 Changed 9 years ago by mf2k (Frank Schima)

Cc: raimue@… removed
Owner: changed from macports-tickets@… to raimue@…
Version: 2.3.4

comment:2 Changed 9 years ago by raimue (Rainer Müller)

Resolution: fixed
Status: newclosed

Thank you for the patch, very good work with all the patch files! I was not aware of the move and also the livecheck did not pick it up as the original website is still online (and only redirects with JavaScript).

Some comments and changes I applied:

  • No need to increase the epoch, the version numbering scheme did not change
  • Release tarballs are preferred over tarballs generated by GitHub
  • Retain bash-completion-devel for the time being until it is properly marked as replaced_by and then removed

Committed with these changes in r148553.

comment:3 in reply to:  2 ; Changed 9 years ago by xeron (Ivan Larionov)

Thank you!

I'm ok with all you changes, but adding some comments just FYI:

  • No need to increase the epoch, the version numbering scheme did not change

For some reason port -u upgrade outdated didn't update it for me until I bumped epoch.

  • 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 :)

  • 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.

Last edited 9 years ago by xeron (Ivan Larionov) (previous) (diff)

comment:4 in reply to:  3 Changed 9 years ago by raimue (Rainer Müller)

Replying to 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.

Note: See TracTickets for help on using tickets.