There were several substitions like "${XXX:S/$/.something/} which is the
equivalent of appending, e.g. "${XXX}.something".
So for the sake of comprehension, change these to appends, and also just
hardcode ".tar.gz" instead of using ${EXTRACT_SUFX} for the same reason.
Since the distfiles are being manually defined, there's no real purpose
to have a variable in the name, and if the EXTRACT_SUFX changes for any
reason (say a new distfile with a different suffix requiring USES+=tar),
then the code actually breaks. These changes make the code easier to
read, comprehend, and arguably makes the port more robust.
The googlecode URL only provides 2.6.0 and 2.6.2 versions of the man pages
and bootstrap compiler, but not the current 2.6.4, so remove those urls.
While here, simplify the LOCAL distcache site urls. The substition is not
necessary.
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.
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
For a while now bsdtar is able to autotermine compression and archive format.
Let's then use tar directly instead of piping to tar.
Now USE_BZIP2 and USE_XZ only set EXTRACT_SUFX to the right format
- make use of optimizations by default, where possible
(quad flavor to follow shortly, and mpi at a later date)
Suggestions and patches from: ache, C. Burns, wen
- Add support for amd64 [1]
- Add 23 new ports to to bsd.fpc.mk
- Remove obsolete patch file patch-packages-fcl-db_Makefile
- Turn off some optional dependencies like databases/unixODBC,
graphics/svgalib, databases/oracle8-client for avoid break amd64 support
- Clean up
PR: ports/146001
Submmitted by: Christopher Key <cjk32__ at _cam.ac.uk>
Patch reviewed by: marcov_ at _pascalprogramming.com (fpc developer)[1]