We could think of the following use cases:
1. User installs git-extras from official port/pkg. man/man* structure
is quite common among different systems, but location of man/ itself can
be different. FreeBSD Ports framework setups MANPREFIX to PREFIX by
default, i.e. it's /usr/local. The idea is that software may provide
different man/man* sections, with final path being /usr/local/man/man*.
In contrast, git-extras' Makefile process simplifies the things due to
it works with section 1 only, and expects MANPREFIX to be set down to
man/man1 path. For this reason, installation via FreeBSD Ports requires
unconditional man path configuration like this:
ifeq ($(OS), FreeBSD)
MANPREFIX = "$(PREFIX)/man/man1"
Otherwise, the path will be incorrect. And this is how official FreeBSD
port of git-extras has been fixing this difference for many years.
2. End user installs git-extras manually. There are two sub-cases:
2.a. User explicitly defines custom MANPREFIX. Okay, it's user's
decision -- nothing to do here, just follow as is.
2.b. User does not define custom paths, i.e. it's expected to be
installed according to FreeBSD defaults. And default values in
git-extras' Makefile forms the expected correct path.
This change supports all the cases above, with the goal to avoid wrong
man path for the most of the situations. As long as official git-extras
make process tries to support FreeBSD, this change allows to omit extra
patching for FreeBSD Ports framework.
|
||
|---|---|---|
| .github/workflows | ||
| bin | ||
| etc | ||
| helper | ||
| man | ||
| .editorconfig | ||
| AUTHORS | ||
| brew-release.patch | ||
| check_dependencies.sh | ||
| check_integrity.sh | ||
| Commands.md | ||
| CONTRIBUTING.md | ||
| History.md | ||
| install.cmd | ||
| install.sh | ||
| Installation.md | ||
| LICENSE | ||
| Makefile | ||
| need_git_commit | ||
| not_need_git_repo | ||
| Readme.md | ||
Git Extras
Little git extras.
Screencasts
Just getting started? Check out these screencasts:
- introduction -- covering git-ignore, git-setup, git-changelog, git-release, git-effort and more
Installation
See Installation page.
Commands
Go to Commands page for basic usage and examples.
GIT utilities -- repo summary, repl, changelog population, author commit percentages and more
Contributing
Interested in contributing? Awesome!
Please read Contributing before you make a PR, thanks!
The change of the default branch
As of Git Extras 6.4 the assumed default branch name changed from master to main.
This affects the Git Extras commands git archive-file, git delete-merged-branches, git delta, git pull-request, git show-merged-branches, git show-unmerged-branches and git squash.
To change the default branch name to master: change either the configuration git-extras.default-branch or init.defaultBranch to master, the former takes precedence.
For example, git config git-extras.default-branch master