FreeBSD Monitor - Feeds::ports_changes http://www.fbsdmon.org/feed/ports_changes 2014-04-23T23:59:59Z FreeBSD Monitor ports_changes http://www.fbsdmon.org/feed/ports_changes/01848e0034d94529e2f2 2014-04-23T23:59:59Z AUTHOR: tijl@FreeBSD.org<br /><br />The semantics of USES=libtool have changed. It now deletes .la libraries<br />from the staging area to reduce overlinking. USES=libtool:keepla can be<br />used in case they need to be kept. This form still modifies .la libraries<br />to remove references to other libraries to reduce overlinking.<br /><br />Note that .la libraries have to kept around as long as there are .la<br />libraries from other ports that refer to them. Those ports need to use<br />some form of USES=libtool first such that those references are removed. ports_changes http://www.fbsdmon.org/feed/ports_changes/6fb2bc5e7d4035b890a2 2014-04-19T23:59:59Z AUTHOR: bdrewery@FreeBSD.org<br /><br />check-orphans has been renamed to check-plist. It now checks:<br /> A. Files in STAGEDIR that are missing from plist.<br /> To make check-plist ignore a file *as an orphan* do one of the<br /> following:<br /> 1. Install it<br /> 2. post-install: ${RM} ${STAGEDIR}file<br /> 3. Put the file behind an OPTION with a PLIST_SUB: %%OPTION%%file<br /> 4. Add to plist as a @comment<br /> @comment file<br /> @comment @dirrmtry dir<br /> B. Files in plist missing from STAGEDIR<br /> C. Files in plist which are owned by dependencies/MTREEs ports_changes http://www.fbsdmon.org/feed/ports_changes/877ba70cc7eab14d6ddc 2014-04-16T23:59:59Z AUTHOR: bdrewery@FreeBSD.org<br /><br />The default target for 'make' now runs 'make stage' if the port supports<br />it, otherwise 'make build' as before. ports_changes http://www.fbsdmon.org/feed/ports_changes/f684af3b29dc23a784e4 2014-04-11T23:59:59Z AUTHOR: bdrewery@FreeBSD.org<br /><br />A new plist keyword has been added, @sample. It accepts a file (must end in<br />.sample):<br /><br /> @sample file.conf.sample<br /><br />This will install file.conf.sample and copy it to file.conf. The file.conf<br />will be removed if it matches file.conf.sample on deinstall.<br /><br />This replaces older patterns of:<br /><br /> @unexec if cmp -s %D/etc/pkgtools.conf %D/etc/pkgtools.conf.sample; then rm -f %D/etc/pkgtools.conf; fi<br /> etc/pkgtools.conf.sample<br /> @exec [ -f %B/pkgtools.conf ] || cp %B/%f %B/pkgtools.conf ports_changes http://www.fbsdmon.org/feed/ports_changes/90d011f28d18c2e9378b 2014-03-12T23:59:59Z AUTHOR: bapt@FreeBSD.org<br /><br />Two new USES were added to finish handling distfiles formats a consistent way:<br /><br />USES=tar[:[xz|bzip2|Z|tgz]] handles distributions files in format:<br />- plain tar<br />- tar.xz<br />- tar.bz2<br />- tar.Z<br />- tgz<br /><br />USES=lha handles distributions files info LHA format ports_changes http://www.fbsdmon.org/feed/ports_changes/3fbc4ec90e70948998f0 2014-03-07T23:59:59Z AUTHOR: rene@FreeBSD.org<br /><br />Two new USES were added by bapt@FreeBSD.org :<br /><br />USES=zip handles distribution files in Zip format. InfoZip files<br />need USES=zip:infozip<br /><br />USES=makeself handles distribution files in makeself format. ports_changes http://www.fbsdmon.org/feed/ports_changes/2b7b39e49abb485d97f6 2014-03-03T23:59:59Z AUTHOR: kde@FreeBSD.org<br /><br />Add support for Qt 5 via USE_QT5. USE_QT5 is analogous to USE_QT4,<br />the only difference is the list of available components<br />(see Mk/bsd.qt.mk for details). USES=qmake supports Qt 5 as well. ports_changes http://www.fbsdmon.org/feed/ports_changes/2281e93742f18ddfa62f 2014-01-27T23:59:59Z AUTHOR: mat@FreeBSD.org<br /><br />Add two new options helpers:<br /><br />${OPT}_${TYPE}_DEPENDS_OFF=&lt;something&gt; will automatically add:<br />${TYPE_DEPENDS}+=&lt;something&gt; in case OPT is 'off'<br /><br />${OPT}_${FLAG}_OFF=&lt;something&gt; will automatically add:<br />${FLAG}+=&lt;something&gt; in case OPT is 'off' ports_changes http://www.fbsdmon.org/feed/ports_changes/78019e0c325190366192 2014-01-27T23:59:59Z AUTHOR: mat@FreeBSD.org<br /><br />Add two new options helpers:<br /> <br />${OPT}_${TYPE}_DEPENDS_OFF=&lt;something&gt; will automatically add:<br />${TYPE_DEPENDS}+=&lt;something&gt; in case OPT is 'off'<br /><br />${OPT}_${FLAG}_OFF=&lt;something&gt; will automatically add:<br />${FLAG}+=&lt;something&gt; in case OPT is 'off' ports_changes http://www.fbsdmon.org/feed/ports_changes/557b894c8ef1a177aac5 2014-01-11T23:59:59Z AUTHOR: mva@FreeBSD.org<br /><br />New USES=uniquefiles to make files or directories unique<br />by adding a prefix or suffix to them.<br /><br />Files listed in UNIQUE_PREFIX_FILES will receive the prefix<br />set via UNIQUE_PREFIX. The same applies to UNIQUE_SUFFIX_FILES,<br />but with the chosen UNIQUE_SUFFIX. UNIQUE_PREFIX and<br />UNIQUE_SUFFIX are set to PKGNAMEPREFIX and PKGNAMESUFFIX by<br />default.<br />The uniquefiles USES enables ports to name files in special<br />ways, e.g. by outlining that the port does not support X11<br />(-nox11). A binary named bin/foo thus can be easily renamed<br />to bin/foo-featureA via<br /><br />USES= uniquefiles<br />UNIQUE_SUFFIX= -featureA<br />UNIQUE_SUFFIX_FILES= bin/foo<br /><br />The uniquefiles USES automatically adjusts the plist at<br />installation time. There is no need to consider the prefix<br />or suffix in the pkg-plist file itself. If the original name<br />of the renamed file is bin/foo, this exact name should be put<br />into pkg-plist.<br /><br />The dirs argument to USES=uniquefiles will cause certain<br />standard directories, such as DOCSDIR or EXAMPLESDIR to be<br />prepended with the UNIQUE_PREFIX. The change to the directories<br />will hapen prior to configuring or building the port, so that<br />the port Makefile as well as the port's build logic are aware<br />of the changed name.<br /><br />Since the uniquefiles USES effectively manipulates the port's<br />installation and file layout, it will only be available for<br />stagedir-aware ports. Ports with NO_STAGE=yes will be unable<br />to use the uniquefiles USES. ports_changes http://www.fbsdmon.org/feed/ports_changes/13c02ed44b096c4ac821 2013-12-18T23:59:59Z AUTHOR: mva@FreeBSD.org<br /><br />lang/python (and as such the 'python' binary and accomplices)<br />has been removed as default dependency for the USE_PYTHON,<br />USE_PYTHON_BUILD and USE_PYTHON_RUN knobs.<br /><br />Ports need to use a designated (default) python interpreter<br />to build and install and in most cases for execution in the user<br />environment. Ports that install python scripts, which are not<br />limited to a certain python version (or version range), can<br />include lang/python as build and/or run dependency.<br /><br />USE_PYTHON=yes and similar knobs will only pull in the<br />default python version (e.g. lang/python27), but none<br />of the meta ports or lang/python itself.<br /><br />Please use lang/python as build or run-time dependency only,<br />if there is no other way to get a port working properly, since<br />the usage of lang/python complicates package builds for different<br />python versions. ports_changes http://www.fbsdmon.org/feed/ports_changes/339956d52ec7ede01c5f 2013-12-13T23:59:59Z AUTHOR: tijl@FreeBSD.org<br /><br />New USES=fortran to replace USE_FORTRAN.<br /><br />USE_FORTRAN=yes can be replaced with USES=fortran or USES=fortran:gcc.<br />USE_FORTRAN=ifort can be replaced with USES=fortran:ifort.<br />USE_FORTRAN=f77 is deprecated and the version of gcc it depends<br />on (lang/gcc34) is scheduled to be removed.<br /><br />Note that USE_FORTRAN=yes also makes GCC the C/C++ compiler while<br />USES=fortran only sets the Fortran compiler and can be used together<br />with Clang as C/C++ compiler. ports_changes http://www.fbsdmon.org/feed/ports_changes/653fe9483f336b9fe7da 2013-12-08T23:59:59Z AUTHOR: mva@FreeBSD.org<br /><br />New USES=twisted, to replace the old USE_TWISTED knob.<br /><br />twisted can be configured with the arguments run or build to replace<br />the previous USE_TWISTED_RUN and USE_TWISTED_BUILD knobs. The twisted<br />components can be added as comma-separated arguments. If you previously<br />wrote<br /> USE_TWISTED= yes<br /> USE_TWISTED= conch names<br /> USE_TWISTED_RUN= yes<br />you now would write<br /> USES= twisted<br /> USES= twisted:conch,names<br /> USES= twisted:run ports_changes http://www.fbsdmon.org/feed/ports_changes/75d256e0bf6d58cf8ee5 2013-11-19T23:59:59Z AUTHOR: kwm@FreeBSD.org<br /><br />The USE_GNOME component ltverhack no longer has a hard dependancy on<br />libtool.<br /><br />If USE_AUTOTOOLS=libtool isn't defined it will try to patch ltmain.sh<br />and or libtool in ${WRKSRC}. If those files are located somewhere else<br />in ${WRKSRC} then it is possible to overwrite ltverhack_PATCH_FILES<br />with there new locations. configure script --distable-static will work also<br />after using the "new" ltverhack.<br /><br />Please keep in mind that USE_AUTOTOOLS implies GNU_CONFIGURE so you might<br />need to add that back for the port to work. ports_changes http://www.fbsdmon.org/feed/ports_changes/d087f0733d32624de82c 2013-11-19T23:59:59Z AUTHOR: kwm@FreeBSD.org<br /><br />The USE_GNOME component ltverhack no longer has a hard dependancy on <br />libtool.<br /><br />If USE_AUTOTOOLS=libtool isn't defined it will try to patch ltmain.sh<br />and or libtool in ${WRKSRC}. If those files are located somewhere else<br />in ${WRKSRC} then it is possible to overwrite ltverhack_PATCH_FILES<br />with there new locations. configure script --distable-static will work also<br />after using the "new" ltverhack.<br /><br />Please keep in mind that USE_AUTOTOOLS implies GNU_CONFIGURE so you might<br />need to add that back for the port to work. ports_changes http://www.fbsdmon.org/feed/ports_changes/293e1f4c80ea8ef5af43 2013-10-31T23:59:59Z AUTHOR: rene@FreeBSD.org<br /><br />Add a new USES for kernel module ports.<br /><br />USES=kmod takes no arguments and:<br />- adds kld to CATEGORIES<br />- sets SSP_UNSAFE<br />- sets IGNORE if the kernel sources are not found<br />- defines KMODDIR to /boot/modules by default, add it to<br />PLIST_SUB and MAKE_ENV, and create it upon installation<br />- handles cross-referencing kernel modules upon installation and<br />deinstallation ports_changes http://www.fbsdmon.org/feed/ports_changes/5da49f477e4f469fb30e 2013-10-31T23:59:59Z AUTHOR: rene@FreeBSD.org<br /><br />Add a new USES for kernel module ports.<br /><br />USES=kmod takes no arguments and:<br />- adds kld to CATEGORIES<br />- sets SSP_UNSAFE<br />- sets IGNORE if the kernel sources are not found<br />- defines KMODDIR to /boot/modules by default, add it to<br /> PLIST_SUB and MAKE_ENV, and create it upon installation<br />- handles cross-referencing kernel modules upon installation and<br /> deinstallation ports_changes http://www.fbsdmon.org/feed/ports_changes/97c3c50451882e5dc2df 2013-10-21T23:59:59Z AUTHOR: amdmi3@FreeBSD.org<br /><br />share/applications directory was added to the mtree, meaning that<br />you no longer need to create or remove it in your ports. ports_changes http://www.fbsdmon.org/feed/ports_changes/f6d2a2e16a6c1bd7af6d 2013-10-08T23:59:59Z AUTHOR: makc@FreeBSD.org<br /><br />New USES: qmake, configure tool widely used among Qt based projects.<br />New framework is stage-friendly. To convert existing ports remove<br />custom configure target, adjust QMAKE_ENV, QMAKE_ARGS, QMAKE_PRO if<br />required (see Mk/Uses/qmake.mk for details). ports_changes http://www.fbsdmon.org/feed/ports_changes/4c0de61ef8cbbac60bd9 2013-10-08T23:59:59Z AUTHOR: bapt@FreeBSD.org<br /><br />New "compiler" USES to be able to select the compiler based on the<br />features it provides.<br />Supported arguments are:<br />- c++11-lang: the port needs a c++11 aware compiler what ever standard<br />library it uses, implies features<br />- c++11-lib: the port needs a c++11 standard library, implies features<br />- c11: the ports needs a c11 aware compiler implies features<br />- features: this will create a COMPILER_FEATURES variable which contains<br />the list of features ${CC} do support, implies env.<br />- env: the COMPILER_TYPE will be set to either gcc or clang.<br /><br />By default the uses will try to use clang33 from ports when nothing in<br />base is relevant except if the user explicitly defines<br />FAVORITE_COMPILER=gcc in his make.conf