Something to be aware of from the release notes:
<snip>
In the next major release (not *this* one), we will change the
behavior of the "git push" command.
When "git push [$there]" does not say what to push, we have used the
traditional "matching" semantics so far (all your branches were sent
to the remote as long as there already are branches of the same name
over there). We will use the "simple" semantics that pushes the
current branch to the branch with the same name, only when the current
branch is set to integrate with that remote branch. There is a user
preference configuration variable "push.default" to change this, and
"git push" will warn about the upcoming change until you set this
variable in this release.
"git branch --set-upstream" is deprecated and may be removed in a
relatively distant future. "git branch [-u|--set-upstream-to]" has
been introduced with a saner order of arguments.
</snip>
Feature safe: yes
Stop using LIBMD_SHA1, it's been useless for a while now. If we want to not
use SHA1 from OpenSSL I can put BLK_SHA1 in, but since nobody has complained
that we silently fell back to OpenSSL I'm going to stick with that for now.
Pass NO_GETTEXT in MAKE_ARGS instead of MAKE_ENV. This actually works
now[1].
PR: [1]: ports/171939
Submitted by: ohauer@
Feature safe: yes
While here add iconv to CONFIGURE_ARGS to resolve build failures under
certain conditions.[1]
PR: [1]: ports/167071
Submitted by: Trond Endrestøl <Trond.Endrestol@ximalas.info>
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
owner. This only happens if the distfile is extracted as a non-root user, which
is why nobody has noticed this before (I imagine not many people extract and
build as non-root). Because it's not a big deal and not likely to hit the
majority of users, I'm not bumping PORTREVISION.
Noticed by: Andrzej Tobola (private mail)
COPYTREE_SHARE. The documentation in the hooks says you should set
executable permissions on the hook before setting it up in a repository,
but if you update git the permissions get reset. Just install the entire
contrib directory with executable bit set.
What we really need is a "COPYTREE_ASIS" that just leaves the permissions as
they are.
Note I am intentionally not bumping PORTREVISION as this is a minor change
and this port gets updated fairly regularly.
PR: ports/163167
Submitted by: Matthias Fechner <idefix@fechner.net>
devel/p5-subversion which will bring in devel/subversion for us.
Furthermore, devel/p5-subversion already honors the WITH_SUBVERSION_VER knob
so there is no need to duplicate that functionality here just to pick the
correct version of subversion.
Discussed with: avg@
- Remove some of the warnings when building with clang by separating
LDFLAGS from CFLAGS. Still some harmless warnings left though.[1]
Submitted by: [1]: sahil@
