	Commit message (Collapse)	Author	Age	Files	Lines
*	Two new USES added to finish handling distfiles formats a consistent way:	bapt	2014-03-12	1	-0/+14
\| \| \| \| \| \| \| \| \| \| \|	USES=tar[:[xz\|bzip2\|Z\|tgz]] handles distributions files in format: - plain tar - tar.xz - tar.bz2 - tar.Z - tgz USES=lha handles distributions files info LHA format
*	Add a note for USES=zip and USES=makeself which were recently added by bapt	rene	2014-03-08	1	-0/+10
\| \| \| \|	Requested by: mat
*	KDE/FreeBSD team is happy to present Qt 5 in ports!	makc	2014-03-04	1	-0/+7
\| \| \| \| \| \| \| \| \| \|	Alberto Villa (avilla@) has done all the hard work to create Qt 5 ports. Trivial update from 5.2.0-beta1 to 5.2.1 by me. Special thanks for Adriaan de Groot <groot@kde.org> for his assistance for Qt-5.2.0 update. Approved by: portmgr (bapt) (for Mk/bsd.port.mk)
*	- Whitespace cleanup	miwi	2014-01-29	1	-11/+11
\|
*	Add two new options helpers:	mat	2014-01-28	1	-0/+11
\| \| \| \| \| \| \| \| \| \| \|	${OPT}_${TYPE}_DEPENDS_OFF=<something> will automatically add: ${TYPE_DEPENDS}+=<something> in case OPT is 'off' ${OPT}_${FLAG}_OFF=<something> will automatically add: ${FLAG}+=<something> in case OPT is 'off' With hat: portmgr Sponsored by: Absolight
*	New USES=uniquefiles to make files or directories unique	mva	2014-01-12	1	-0/+38
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	by adding a prefix or suffix to them. Files listed in UNIQUE_PREFIX_FILES will receive the prefix set via UNIQUE_PREFIX. The same applies to UNIQUE_SUFFIX_FILES, but with the chosen UNIQUE_SUFFIX. UNIQUE_PREFIX and UNIQUE_SUFFIX are set to PKGNAMEPREFIX and PKGNAMESUFFIX by default. The uniquefiles USES enables ports to name files in special ways, e.g. by outlining that the port does not support X11 (-nox11). A binary named bin/foo thus can be easily renamed to bin/foo-featureA via USES= uniquefiles UNIQUE_SUFFIX= -featureA UNIQUE_SUFFIX_FILES= bin/foo The uniquefiles USES automatically adjusts the plist at installation time. There is no need to consider the prefix or suffix in the pkg-plist file itself. If the original name of the renamed file is bin/foo, this exact name should be put into pkg-plist. The dirs argument to USES=uniquefiles will cause certain standard directories, such as DOCSDIR or EXAMPLESDIR to be prepended with the UNIQUE_PREFIX. The change to the directories will hapen prior to configuring or building the port, so that the port Makefile as well as the port's build logic are aware of the changed name. Since the uniquefiles USES effectively manipulates the port's installation and file layout, it will only be available for stagedir-aware ports. Ports with NO_STAGE=yes will be unable to use the uniquefiles USES. Reviewed by: portmgr@ Approved by: portmgr@
*	- Remove lang/python as implicit build and run dependency from	mva	2013-12-19	1	-0/+22
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	bsd.python.mk Ports need to use a designated python interpreter, whether this is the default one chosen by the user (or provided by the system) and pulled in via USE_PYTHON[_BUILD\|_RUN]=yes or an explicit version or version range pulled in via USE_PYTHON[_BUILD\|_RUN]=X.Y does not matter. Ports should however not rely on 'python' at build or installation time, whenever possible to avoid problems with building packages for different python versions. This change tries to raise the barrier for misbehaving ports and eases package builds for different python versions. Tested with: exp-run (ports/184591) Reviewed by: wg@, koobs@ Supported by: wg@ With hat on: python@
*	New USES=fortran to replace USE_FORTRAN.	tijl	2013-12-13	1	-0/+14
\| \| \| \| \| \| \| \| \| \| \|	USE_FORTRAN=yes can be replaced with USES=fortran or USES=fortran:gcc. USE_FORTRAN=ifort can be replaced with USES=fortran:ifort. USE_FORTRAN=f77 is deprecated and the version of gcc it depends on (lang/gcc34) is scheduled to be removed. Note that USE_FORTRAN=yes also makes GCC the C/C++ compiler while USES=fortran only sets the Fortran compiler and can be used together with Clang as C/C++ compiler.
*	New USES=twisted, to replace the old USE_TWISTED knob.	mva	2013-12-08	1	-0/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	twisted can be configured with the arguments run or build to replace the previous USE_TWISTED_RUN and USE_TWISTED_BUILD knobs. The twisted components can be added as comma-separated arguments. If you previously wrote USE_TWISTED= yes USE_TWISTED= conch names USE_TWISTED_RUN= yes you now would write USES= twisted USES= twisted:conch,names USES= twisted:run
*	Remove ltverhack's hard depend on USE_AUTOTOOLS=libtool.	kwm	2013-11-20	1	-0/+15
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The problem with the old method is that the libtool is configured to look first in LOCALBASE for libraries to link to. Normaly this wouldn't cause a problem. However if a port that builds a library with new API also builds introspection files or say gtk bindings, then libtool will look first into LOCALBASE and find the old library version for linking the introspection files or gtk bindings. Due to the missing new API in old library the build will fail with unresolved symbols. The new ltverhack will patch the ltmain.sh and/or libtool files that where bundled with the port. This libtool is correctly configured to first look in for the just build libraries. If the port bundled version of ltmain.sh and/or libtool aren't in ${WRKSRC} then ltverhack_PATCH_FILES can be overwritten with there location in ${WRKSRC}. As a bonus when using the new ltverhack configure will honor --disable-static again. So please check your plist after converting. While here shorten the number of tabs in the lthacks, ltverhack and ltasneededhack PRE_PATCH components so they are just over 80 chars long. Exp-run by: bdrewery@ PR: ports/183936 Obtained from: gnome dev repo