# Created by: nork@FreeBSD.org # $FreeBSD$ PORTNAME= viPlugin PORTVERSION= 1.14.0 PORTREVISION= 4 CATEGORIES= java devel editors MASTER_SITES= http://www.satokar.com/viplugin/files/ PKGNAMEPREFIX= eclipse- DISTNAME= ${PORTNAME}_${PORTVERSION}_E30 DIST_SUBDIR= eclipse MAINTAINER= freebsd-eclipse@FreeBSD.org COMMENT= Vi like keybinding Eclipse plugin FREETRIAL Version RUN_DEPENDS= ${LOCALBASE}/bin/eclipse:${PORTSDIR}/java/eclipse NO_WRKSUBDIR= yes NO_BUILD= yes USE_ZIP= yes USE_JAVA= yes JAVA_VERSION= 1.6+ JAVA_OS= native PLIST_SUB= RELEASEVERSION=${PORTVERSION} do-install: @${MKDIR} ${PREFIX}/lib/eclipse @${CP} -r ${WRKSRC}/plugins ${PREFIX}/lib/eclipse @${CP} -r ${WRKSRC}/features ${PREFIX}/lib/eclipse .include he log file after each request. If this is turned off there's a slight savings in CPU cycles.
- LOG_UNKNOWN: whether to log unknown request headers.  Most sites will not
  want to log them, which will save them a bit of CPU time;

- FLUSH_LOG: whether to fflush() the log file after each request.  If this
  is turned off there's a slight savings in CPU cycles.
- Make thttpd's collecting of internal stats and printing them to system 2016-07-02T05:54:12+00:00 danfe danfe@FreeBSD.org 2016-07-02T05:54:12+00:00 f19e247164b83ca45484471600b5e38a4ec1b504 log every hour optional, because apparently some users do not want it - Convert to option helper targets (post-patch-FOO-off) while here, which allows us to remove `.include <bsd.port.options.mk>' PR: 200884
  log every hour optional, because apparently some users do not want it
- Convert to option helper targets (post-patch-FOO-off) while here, which
  allows us to remove `.include <bsd.port.options.mk>'

PR:	200884
Another attempt to make `www/thttpd' multiple make(1) jobs (-jX) safe. 2016-06-27T09:08:35+00:00 danfe danfe@FreeBSD.org 2016-06-27T09:08:35+00:00 3a9e775516786ae306ea8980d664bc046bd44b67 During the build process there is one case when parts (source files) are located in different directories and then linked together. Dependencies are specified seemingly correctly, but the problem is that the build rule `$(CC) $(CFLAGS) -c $*.c' loses information about source file path due to how `$*' is expanded ("no suffix or preceding directory components") and does not specify output object path. Change it to more robust and correct `$(CC) $(CFLAGS) -o $@ -c $<' as a remedy. Since this is BSD syntax, remove `gmake' from USES. Tested by: marino (looks good, but not a complete guarantee)
During the build process there is one case when parts (source files) are
located in different directories and then linked together.  Dependencies
are specified seemingly correctly, but the problem is that the build rule
`$(CC) $(CFLAGS) -c $*.c' loses information about source file path due to
how `$*' is expanded ("no suffix or preceding directory components") and
does not specify output object path.

Change it to more robust and correct `$(CC) $(CFLAGS) -o $@ -c $<' as a
remedy.  Since this is BSD syntax, remove `gmake' from USES.

Tested by:	marino (looks good, but not a complete guarantee)
- Update `www/thttpd' to version 2.27 [1] 2016-06-27T06:17:38+00:00 danfe danfe@FreeBSD.org 2016-06-27T06:17:38+00:00 502edee6af22c0f6d7ac8b1d80df2a7dd712160d - Install logfile rotation rule to prevent people running out of space in their /var partitions [2] - Provide an optional patch for IP-based authorization (.htaccess) [3] - While here, do not capitalize `Web' in the middle of the sentence inside `files/pkg-message.in' as it looks like a relic of the 1990s PR: 210040 [1] Submitted by: phk [2] Obtained from: http://ogris.de/thttpd/ [3]
- Install logfile rotation rule to prevent people running out of space
  in their /var partitions [2]
- Provide an optional patch for IP-based authorization (.htaccess) [3]
- While here, do not capitalize `Web' in the middle of the sentence
  inside `files/pkg-message.in' as it looks like a relic of the 1990s

PR:		210040 [1]
Submitted by:	phk [2]
Obtained from:	http://ogris.de/thttpd/ [3]