Mirror the distfile on LOCAL as a http backup for clients that
can't use https.
Use INSTALL_TARGET=install-strip instead of ${STRIP_CMD}.
Differential Revision: https://reviews.freebsd.org/D1473
Approved by: mat (mentor)
- Install desktop and icon files when GNOME or GTK option is set. [1]
- Fix pidfile when 'distccd_flags' variable is not set by the user.
- Replace COMPILER_LINKS option with CLANGLINK and LLVMLINK options. Note
these are turned off by default unlike COMPILER_LINKS. Actually, these are
equivalent to options for devel/ccache as they are often jointly used.
- Modernize and clean up the port.
PR: 185426 [1]
needing to add more targets to STAGE_SEQ. This is especially useful for
customizing the ports tree/framework without modifying bsd.port.mk.
With hat: portmgr
Discussed with: mat
- install policyd-weight.conf with the @sample macro
- alert user if any of this deprecated lists is found in policyd-weight.conf
dnsbl.njabl.org
rbl.ipv6-world.net
rhsbl.ahbl.org
dsn.rfc-ignorant.org
postmaster.rfc-ignorant.org
abuse.rfc-ignorant.org
[1] Noted by: Herbert J. Skuhra
MFH: 2015Q1
The Free Pascal Compiler port currently mandates that the bootstrap
compiler be the same version of the compiler being built. This means that
every update requires a new bootstrap compiler to be generated before the
update. This goes against the philosophy of a bootstrap compiler, which
aims to allow older compilers to build self-hosting modern compilers. FPC
is capable of this, but the feature wasn't being leveraged.
There are a lot of changes in this commit, but I believe the resulting
compiler is the same as before the commit, thus PORTREVISION has not been
bumped. Changes include:
* Add DragonFly bootstrap compiler 2.6.4 to list of distfiles
* use OPSYS to make builds generic between FreeBSD and DragonFly
* Add FREEBSD PLIST variable as FreeBSD builds an extra unit
* Create the framework to have a bootstrap compiler of an older version
than the current version (BOOTVER variable)
* split PP variable out of MAKE_ARGS and use NEWPPC or BOOTPPC to
specify PP uniquely (required when bootstrap version is different)
* wrap compound command with parenthesis
* Use options lists on TAR man page (xfz without hyphen is legacy)
* unmask installation commands
* respect 80-column limits, wrapping as necessary
* bring in some dports-specific changes that have no effect on port
to eliminate dports patch files
future work:
When version 3.0 is released, the new fpc make program will be built
which will have some moderate impacts to the build process and it
will use a "bootstrap" target.
The intention is to continue using the 2.6.4 bootstrap compilers to
build the upcoming 3.0 compiler when it is released. New bootstrap
compilers will not be generated until the existing bootstrap compilers
are unable to bootstrap the upcoming release.
