1. 01 Mar, 2019 1 commit
  2. 01 Jan, 2019 1 commit
  3. 30 Dec, 2018 1 commit
  4. 25 Dec, 2018 1 commit
    • tcberner's avatar
      Change cmake default behaviour to outsource. · 49081780
      tcberner authored
      Ports that build out of source now simply can use "USES=cmake"
      instead of "USES=cmake:outsource". Ports that fail to build
      out of source now need to specify "USES=cmake:insource".
      I tried to only set insource where explictely needed.
      PR:		232038
      Exp-run by:	antoine
  5. 10 Nov, 2018 1 commit
    • bapt's avatar
      Install texinfo files (GNU info) into ${PREFIX}/share/info · 2ac1593f
      bapt authored
      After a discussion on the mailing list on moving manpages to
      ${PREFIX}/share/man for consistency with base where it is
      installed in usr/share/man, it appeared the same should happen
      to GNU info files which were installed under share in base and
      not in ports.
      Now texinfo is not in base on any of the supported version of FreeBSD
      it is possible to proceed to this move and it is easier to do than
      the manpage change.
      Other benefit than consistency are less patching: all build tools but
      cmake are expecting info files to be under share/info and cmake (patched here)
      was having an exception for BSD so the patch makes FreeBSD case less
      specific for them
      Bump revision of all impacted ports
      PR:		232907
      exp-run by:	antoine
      Differential Revision:	https://reviews.freebsd.org/D17816
  6. 28 Jun, 2018 1 commit
  7. 22 May, 2018 1 commit
  8. 07 May, 2018 1 commit
  9. 11 Mar, 2018 1 commit
    • brnrd's avatar
      Mk/Uses/apache.mk: Migrate Mk/bsd.apache.mk to Uses · f9df425c
      brnrd authored
       - Chase required changes in framework (bsd.sanity.mk, bsd.port.mk)
       - Chase required changes in ports (version checks)
       - Chase required changes in PHP ports (include bsd.apache.mk)
       - exp-run by antoine, brnrd, joneum
      PR:             223691 (exp-run)
      Reviewed by:    joneum (hat apache), mat (portmgr), antoine (portmgr)
      Approved by:    joneum (hat apache)
      Approved by:	portmgr
      With hat:       apache
  10. 08 Mar, 2018 1 commit
    • mat's avatar
      Introduce PHP flavors. · 3de11f75
      mat authored
        Ports using USES=php:phpize, php:ext, php:zend, and php:pecl are now
        flavored.  They will automatically get flavors (php56, php70, php71, php72)
        depending of the versions they support (set with IGNORE_WITH_PHP).  As a
        consequence, ports using USES=pear and USES=horde are also flavored.
      PR:		226242
      Submitted by:	mat
      Exp-run by:	antoine
      Approved by:	portmgr
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D14208
  11. 25 Jan, 2018 1 commit
    • mat's avatar
      Add support to passing directories to EXTRA_PATCHES. · 7fdfe1db
      mat authored
      Instead of:
        EXTRA_PATCHES=	${PATCHDIR}/feat-foo-patch-file.c \
      			${PATCHDIR}/feat-foo-patch-file.h \
      Move those files to ${PATCHDIR}/feat-foo/, name them patch-*, and set:
        EXTRA_PATCHES=	${PATCHDIR}/feat-foo
      Approved by:	bdrewery
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D10855
  12. 21 Jan, 2018 1 commit
  13. 06 Jan, 2018 1 commit
    • rakuco's avatar
      Update Qt5 ports to 5.9.3. · 4aff115f
      rakuco authored
      This took quite a lot of time because Qt's own build system underwent
      several changes in 5.8.0 that took a while to adapt to.
      And, of course, qt5-webengine is a behemoth that we need to patch like crazy
      due to its bundling of Chromium. In fact, most of the Chromium patches in
      qt5-webengine have been imported with no changes from www/chromium@433510
      ("www/chromium: update to 56.0.2924.87").
      New port: accessibility/qt5-speech
      Bigger changes to Qt5 ports we had to make:
      - Qt now allows using a configure.json file to define configuration options
        and specify configuration checks that can be done when qmake is invoked.
        However, configure.json checks done in a subdirectory only propagates to
        subdirectories, and checks elsewhere will fail if all .pro files are being
        parsed at once (i.e. qmake -recursive), so several ports had to switch to
        USES=qmake:norecursive along with manual additional qmake invocations in
        subdirectories in order to work. It's been mentioned in a few places such
        as Qt's bug tracker that qmake's recursive mode is pretty much deprecated,
        so we might switch to non-recursive mode by default in the future.
      - Uses/qmake.mk: Introduce QMAKE_CONFIGURE_ARGS. qmake now accepts
        arbitrary options such as '-foo' and '-no-bar' at the end of the
        command-line. They can be specified in QMAKE_CONFIGURE_ARGS.
      - graphics/qt5-wayland: The port can only be built if graphics/mesa-libs is
        built with the WAYLAND option, so a corresponding option (off by default)
        was added to the port.
      - misc/qt5-doc: Switch to a pre-built documentation tarball. The existing
        port was not working with Qt 5.9. Instead of trying to fix it, switch to
        what Gentoo does and fetch a tarball that already contains all
        documentation so that we do not have to build anything at all. The
        tarball's name and location in download.qt.io look a bit weird, but it
        seems to work fine.
      - www/qt5-webengine: Use binutils from ports, Chromium's GN build system
        generates a build.ninja that uses ar(1) with the @file syntax that is not
        supported by BSD ar, so we need to use GNU ar from binutils.
      - x11-toolkits/qt5-declarative-render2d: This port was merged into the main
        Qt Declarative repository upstream, and into x11-toolkits/qt5-quick in the
        ports tree.
      Changes to other ports we had to make:
      - biology/ugene: Drop a '#define point "."' that is not present in more
        recent versions of the port. Defining a macro with such a common name
        causes build issues with Qt 5.9, which uses |point| as an argument name in
      - cad/qelectrotech: Fix plist with Qt 5.9. Directories are no longer
        installed with `cp -f -R', but rather `qmake install qinstall', which does
        not install
        That's a local file that should not even have been part of the tarball
      - chinese/gcin-qt5: Add additional private Qt directories (which should not
        be used in the first place) to get the port to build with Qt 5.9.
      - devel/qtcreator: Fix plist with Qt 5.9. Something changed in qdoc and some
        test classes no longer generate documentation files.
      - security/keepassx-devel: Import a patch sent upstream almost a year ago to
        fix the build with Qt 5.9.
      Thanks to antoine for the exp-run, and tcberner and Laurent Cimon
      <laurent@nuxi.ca> for landing changes in our qt-5.9 branch.
      PR:		224849
  14. 02 Jan, 2018 1 commit
    • tcberner's avatar
      New USES=eigen · 98f12cd7
      tcberner authored
          version: 2 or 3 (required)
          type:    build (default), run
        For example:
        will add a BUILD- and RUN_DEPENDS on math/eigen2, and
        will add a BUILD_DEPENDS on math/eigen3.
      * Convert the existing ports to use it
        - biology/iqtree: remove run time dependency (seemed not to be needed)
        - graphics/movit: remove run time dependency (seemed not to be needed)
        - science/avogadro: add run time dependeny (installed cmake file requires it to be present)
      Reviewed by:	rakuco, mat
      Differential Revision:	https://reviews.freebsd.org/D13702
  15. 31 Dec, 2017 1 commit
    • tcberner's avatar
      Add CMAKE_ON and CMAKE_OFF to cmake.mk · 7d25ef3c
      tcberner authored
        USES=cmake now supports two additional list variables:
          * CMAKE_ON  : List of variables to turn on
          * CMAKE_OFF : List of variables to turn off
        This can be used as a shortcut to append these to CMAKE_ARGS.
        For example ports that previously set
        can now set this as
          CMAKE_ON=		VAR1 VAR2
          CMAKE_OFF=		VAR3
      Reviewed by:	adridg, rakuco, mat
      Differential Revision:	https://reviews.freebsd.org/D13636
  16. 14 Dec, 2017 3 commits
  17. 11 Dec, 2017 1 commit
  18. 30 Nov, 2017 4 commits
    • bdrewery's avatar
      Add link for guides on FLAVORS · 958de635
      bdrewery authored
    • mat's avatar
      Convert Python ports to FLAVORS. · 32512cab
      mat authored
        Ports using USE_PYTHON=distutils are now flavored.  They will
        automatically get flavors (py27, py34, py35, py36) depending on what
        versions they support.
        There is also a USE_PYTHON=flavors for ports that do not use distutils
        but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
        using distutils but flavors are not wanted.
        A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
        added to cope with Python ports that did not have the Python
        PKGNAMEPREFIX but are flavored.
        USES=python now also exports a PY_FLAVOR variable that contains the
        current python flavor.  It can be used in dependency lines when the
        port itself is not python flavored.  For example, deskutils/calibre.
        By default, all the flavors are generated.  To only generate flavors
        for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
        BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
        In all the ports with Python dependencies, the *_DEPENDS entries MUST
        end with the flavor so that the framework knows which to build/use.
        This is done by appending '@${PY_FLAVOR}' after the origin (or
        @${FLAVOR} if in a Python module with Python flavors, as the content
        will be the same).  For example:
          RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
      PR:		223071
      Reviewed by:	portmgr, python
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D12464
    • mat's avatar
      Add various FLAVOR related helpers. · 87acdef7
      mat authored
        To help with flavored ports, helpers are available.  In these, replace <*>
        with the flavor name.
        *_PKGNAMEPREFIX *_PKGNAMESUFFIX *_PLIST *_DESCR will overwrite the variable.
        *_LIB_DEPENDS *_RUN_DEPENDS *_TEST_DEPENDS will append to the variable.
      Reviewed by:	portmgr
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D12483
    • mat's avatar
      Generic FLAVORS work. · 4b9fac22
      mat authored
      - Enable FLAVORS.
      - Make make describe flavors aware.
      - Add a qa check for unique package names amongst flavors.
      - Make MOVEDlint understand flavors.
      - Add a bit of sanity check to make sure FLAVORS stay lowercase.
      - Various fixes.
      Reviewed by:	portmgr
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D12577
  19. 20 Oct, 2017 1 commit
  20. 12 Oct, 2017 1 commit
  21. 11 Oct, 2017 1 commit
    • bapt's avatar
      Introduce the new BINARY_ALIAS variable · 3edb1756
      bapt authored
      When defined it will create symlinks of some given binaries in a directory which
      will be prepended to the PATH.
      The syntax is the following:
      BINARY_ALIAS=   target1=source1  target2=source2
      For example to have a "swig" binary in the path which will be pointing at
      swig3.0 and a "sed" pointing at GNU sed: gsed
      BINARY_ALIAS=  swig=swig3.0 sed=gsed
      Reviewed by:	swills, adamw, mat
      Approved by:	swills (portmgr)
      Differential Revision:	https://reviews.freebsd.org/D12603
  22. 25 Jun, 2017 1 commit
    • tcberner's avatar
      Make ninja opt-out in cmake.mk · 19b60f63
      tcberner authored
      Using ninja instead of make (1) can lead to significant speed ups while building.
      Therefore switch from having the ninja generator opt-in to having it opt-out.
      Previously cmake-ports that wanted to use ninja could set
      now, ports that do not work with ninja can set
          cmake:<existing args>,noninja
      Note, that needing this should be an exception and most often points to a broken
      cmake of the port.
      The ports using cmake were modified
      * removed USES=gmake, if ninja is used
      * removed MAKE_ARGS, if ninja is used
      * added the cmake-argument noninja if necessary
      PR:		219629
      PR:		213331
      Exp-run by:	antoine
      Reviewed by:	rakuco
      Differential Revision:	https://reviews.freebsd.org/D10748
  23. 04 Jun, 2017 1 commit
  24. 17 Apr, 2017 1 commit
  25. 13 Mar, 2017 1 commit
  26. 18 Feb, 2017 1 commit
    • tcberner's avatar
      Update Qt5 to 5.7.1, and unify the Qt4 and Qt5 ports some more · 3b326c79
      tcberner authored
      * Update Qt5 to 5.7.1
      * Move Qt4 binaries to lib/qt4/bin
      * Move Qt5 libraries to lib/qt5/lib
        By moving the libraries we should finally be able to get rid of the inplace
        upgrade bug (see ports bugs 194088, 195105 and 198720):  when Qt5's libraries
        were lying in /usr/local/lib, which would often get added by pkgconfig to the
        linker paths via dependencies, the already installed libraries were linked
        against, instead of the ones that were being built. This forced us to make
        sure, that -L${WRKSRC}/lib was always coming before -L/usr/local/lib in the
        linker flags. With this change this should no longer be the case.
      * Rename some ports to match the rest (foo-qtX -> qtX-foo)
      * Depend on new port misc/qtchooser [see UPDATING & CHANGES]
      There are several new Qt5 ports which all have been created by Marie Loise Nolden
      <nolden@kde.org>. Thanks again.
      PR:		216797
      Exp-Run by:	antoine
      Reviewed by:	rakuco, mat, groot_kde.org
      Approved by:	rakuco (mentor)
      Differential Revision:	https://reviews.freebsd.org/D9213
  27. 16 Jan, 2017 2 commits
  28. 18 Dec, 2016 1 commit
  29. 13 Sep, 2016 1 commit
  30. 09 Sep, 2016 1 commit
    • amdmi3's avatar
      Most commonly used build systems support silent builds, when they · 6e502d51
      amdmi3 authored
      hide actual commands executed and only show short summary line (like
      "CC foo.c"). CMake and ninja enable this by default, some autotools
      using ports do as well. This is unacceptable because we need complete
      build logs at any time, so we now switch to verbose build logs
      unconditionally. Note that this change deliberately affects ALL
      builds and not only package builds on cluster, because we need to
      be sure that user experiencing failure can always provide informative
      build log regardless of settings and without rerunning the build.
      Change summary:
      - Always do verbose builds for cmake, ninja and GNU configure (the
        latter includes check if --disable-silent-rules is actually supported
        by the configure script; there are isolated cases when it's not true)
        CONFIGURE_ARGS=--disable-silent-rules from all ports which set them
        for this is no longer needed
      - Revert hacks for --disable-silent-rules support priorly committed
        to biology/ncbi-blast+ and net-p2p/mldonkey - no longer needed as well
      Submitted by:	amdmi3
      Reviewed by:	mat
      Exp-run by:	antoine
      Approved by:	portmgr (mat, antoine)
      Differential Revision:	D7534
  31. 08 Sep, 2016 1 commit
    • amdmi3's avatar
      Add support added for LICENSE=NONE, use it when the port doesn't · 8841734a
      amdmi3 authored
      have cleanly defined licensing terms.  Note that without clean
      license allowing you to use and distribute the code it would be be
      illegal to do so in many jurisdictions, so for ports with NONE
      license no distfiles or packages are distributed.
      While here, fix trailing whitespace in CHANGES.
      Approved by:	portmgr (bapt)
      Differential Revision:	D7816
  32. 26 Aug, 2016 1 commit
  33. 24 Aug, 2016 2 commits
    • mat's avatar
      Add GH_SUBDIR, automatically moves a secondary distfile to the right · 68c70f03
      mat authored
      place inside ${WRKSRC}.
      GH_TUPLE=	Regaddi:Chart.js:f13f99b:chart_js \
      	@${RMDIR} ${WRKSRC}/database ${WRKSRC}/3rd/Chart.js
      	@${MV} ${WRKSRC_database} ${WRKSRC}/database
      	@${MV} ${WRKSRC_chart_js} ${WRKSRC}/3rd/Chart.js
      GH_TUPLE=	Regaddi:Chart.js:f13f99b:chart_js/3rd/Chart.js \
      Sponsored by:	Absolight
      Differential Revision:	https://reviews.freebsd.org/D7583
    • tcberner's avatar
      Replace Mk/bsd.kde4.mk by Mk/Uses/kde.mk in preparation for KDE Frameworks and · a5fddeaf
      tcberner authored
      Plasma5 ports
      At the moment KDE ports use bsd.kde4.mk to handle their dependencies. When
      working on the ports for KDE Frameworks and Plasma5 it seemed to be more
      reasonable to create a new kde.mk instead of adding an bsd.kde5.mk.
      The kde.mk in this review is a stripped down version of the one we are using in
      the KDE Test repositories plasma5 branch [1] to only contain the parts relevant
      to the current KDE4 ports in the portstree [2].
      Changes to the KDE Ports needed by this:
      Replace USE_KDE4 by USE_KDE [3]
      Add USES=kde:4 [4]
      [1] http://src.mouf.net/area51/view/branches/plasma5/KDE/Mk/Uses/kde.mk
      [2] The version in the plasma5 branch also handles frameworks/plasma5 and
          handles MASTER_SITES via a KDE_DIST variable similar to bsd.qt.mk for Qt
          Ports -- I chose to leave this out for now, as the diff is already large
      [3] I chose USE_KDE instead of USE_KDE4, USE_KDE5, USE_KDEX as the version we
          want is already specified as argument to kde:<arg>
      [4] For KDE Frameworks and Plasma5 ports this would be kde:5
      PR:             210667
      Approved by:    portmgr, mat (mentor), rakuco (mentor)
      Reviewed by:    mat, rakuco
      Differential Revision:   https://reviews.freebsd.org/D6961