New Port: git-flow-bash-completion

[gorticus (Jason Mitchell)]

Bash (and Zsh) completion support for git-flow

The contained completion routines provide support for completing:

• git-flow init, feature, hotfix and release
• feature, hotfix and release branches
• remote feature branch names (for git-flow feature track)

Project homepage: ​http://github.com/bobthecow/git-flow-completion

NOTES:

• For use with git-flow; see New Port ticket #26803.
• provides bash completion only, no zsh
• expects git >= 1.7.1 to avoid hand editing /path/to/bash_completion.d/git

[raimue (Rainer Müller)]

In my opinion this should be added as a +bash_completion variant in git-flow.

[gorticus (Jason Mitchell)]

I agree, but since I'm a n00b, it's a separate pkg, and I wasn't sure how the variants interacted w/ 'fetch.type git', I left it separate.

If you can point me to a dual git pull example, I'll give it a shot.

[robsonpeixoto@…]

But the git-flow-completion has your own lifecycle.

I'm attaching a version using PortGroup github

[robsonpeixoto@…]

Version 0.4.2 using PortGroup github

[gorticus (Jason Mitchell)]

Replying to robsonpeixoto@…:

But the git-flow-completion has your own lifecycle.

I'm attaching a version using PortGroup github

Nice. Much more concise.

While I'm no expert, I have a few suggestions/questions, based on port lint:

• name needs to be set to git-flow-bash-completion indicate bash only
• the distribution license is MIT as indicated on the homepage
• category is not set by portgroup
• does copy ensure the correct permissions? (Tcl is a 4th+ language for me)
• add openmaintainer
• # $Id$ is required
• platforms is required (darwin)

Suggestions are included in Portfile.3 attached.

[gorticus (Jason Mitchell)]

few suggestions on Portfile.2

[gorticus (Jason Mitchell)]

Replying to robsonpeixoto@…:

But the git-flow-completion has your own lifecycle.

I'm attaching a version using PortGroup github

I should probably update git-flow based on your portgroup changes. I checked ffmpeg and it should be straightforward to make this an option for git-flow, but as you correctly noted, would require separate updates since the lifecycle is separate, but related.

[neverpanic (Clemens Lang)]

I agree this would better be integrated into the git-flow ports, but now that there are a lot of them and given the separate lifecycles I'm not exactly sure how I'd achieve that either. I'm committing as-is to avoid leaving this laying around for an even longer time. r122829.