- Add new options [2]
while here
- Add libtool to USES
- Silence mkdir and post-patch commands
Patch improved by Daniel Salzman <daniel.salzman@nic.cz> [2]
PR: ports/190370
Submitted by: Leo Vandewoestijne <freebsd@dns-lab.com> (maintainer) [1]
Recently DragonFly was added as an officially supported platform on
GCC, providing OOTB support for C, C++, ObjC, and Fortran. However,
the Java lang does not build, even if the first failure (boehm-gc) is
fixed.
Adding Makefile.DragonFly is the cleanest and least intrusive way I could
remove the JAVA option (there is no EXCLUDE_OPTION_${OPSYS} support in
bsd.options.mk)
Approved by: maintainer (gerald@)
I can tell lifetype is a really old port. In addition to staging, I
took the liberty to:
* convert roll-your-own pkg-message to SUB_FILES/SUB_LIST
* convert roll-your-own PLIST to TMPPLIST
* Remove leading article from comment
* Fix double-extraction bug (templates and plugins extracted twice in
two different places) by using EXTRACT_ONLY
* Add a license (GPLv2)
* Use ".zip" instead of EXTRACT_SUFX for aesthetic reasons, the variable
didn't help since the rest of the file name was hardcoded
* Rewrite package list autogen and move it from pre-install target to
post-install target. It's needed because templates, plugins change all
the time and even without it's 4000 line plist (200kb+)
* Remove imagick option, it doesn't seem to be a php extension anymore
as far as I can tell. It was missing USE_PHP+= imagick in any case
* Remove references to imagick option, rewrite pre-patch warning
* Add USE_PHP+= gd to gd option to fix it
* Use TAR instead of EXTRACT_CMD or UNZIP_CMD to extract the templates and
plugins (unzip still used for main distfile). UNZIP_CMD current refers
to infozip which isn't a dependency. To avoid using EXTRACT_CMD and
adding a new dependency on infozip, TAR was deemed the best choice since
it clearly works fine.
This work was done independently of PR: ports/190214
The default extract target can be used if NO_WRKSUBDIR is set. The
only unique command is the gunzip, which works well as a post-extract
target. This eliminates the undefined use of EXTRACT_CMD to ensure
the port keeps working in the future.
The code itself may be distributed, as well as compiled binaries.
But its usage is subject to patent restrictions, as indicated to the
user in pkg-message.
While on it:
- Stagify
- Pet portlint
PR: ports/189093
Submitted by: Jason Bacon <jwbacon@tds.net>
Approved by: thierry (mentor)
The staging attempted didn't go quite right as it was hardcoded for
FreeBSD 9 AMD. Since I'm fixing this anyway, bring in dports patches
to support DragonFly.
This port has distfiles of two formats: .tar.bz2 and .tar.gz.
The TAR command handles both of them, so explicit specify this tool
to ensure the port continues to work in the future.
As a comment, it's strange that a custom extract target is needed to
overcome a possible deficiency in the standard extract target.
