/japanese/skkinput/

sd-ports-gnome/'>freebsd-ports-gnome
FreeBSD GNOME current development ports (https://github.com/freebsd/freebsd-ports-gnome)
aboutsummaryrefslogtreecommitdiffstats
path: root/x11/cinnamon
Commit message (Collapse)AuthorAgeFilesLines
* - Those ports fail to build with python3antoine2017-12-121-4/+4
| | | | - Add some explicit FLAVOR to dependencies where needed
* Bump PORTREVISION for ports depending on the canonical version of GCCgerald2017-09-111-1/+1
| | | | | | | | | | | | | | (via Mk/bsd.default-versions.mk and lang/gcc) which has moved from GCC 5.4 to GCC 6.4 under most circumstances. This includes ports - with USE_GCC=yes or USE_GCC=any, - with USES=fortran, - using Mk/bsd.octave.mk which in turn features USES=fortran, and - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang, c++14-lang, c++0x, c11, or gcc-c++11-lib. PR: 219275
* Chase evolution-data-server shared library bump.kwm2017-06-131-1/+1
|
* Chase evolution-data-server shlib bumps.kwm2017-05-171-1/+1
|
* Fix the build fix. Copy paste fat finger, the copy buffer contained the ↵kwm2017-05-121-1/+1
| | | | | | | | incorrect version of the fix. And I didn't check the paste. Reported by: Thomas Gellekum <thomas.gellekum@netaachen.de>
* Don't error out on warnings during introspection build.kwm2017-05-111-0/+2
|
* Bump PORTREVISIONs for ports depending on the canonical version of GCC andgerald2017-04-011-1/+1
| | | | | | | | | | | | | | lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some circumstances such as versions of FreeBSD or platforms). This includes ports - with USE_GCC=yes or USE_GCC=any, - with USES=fortran, - using using Mk/bsd.octave.mk which in turn has USES=fortran, and - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang, c++11-lang, c++0x, c11, or gcc-c++11-lib. PR: 216707
* Never set WRKSRC when using USE_GITHUB.mat2017-01-042-4/+6
| | | | | | | | | | If you want to set WRKSRC, set GH_PROJECT instead. - The GitHub URLs are case insensitive, but the distribution files you get out of them are not. - If the repository was renamed, the old URL will still work, but the distribution name will be ith the new name. Sponsored by: Absolight
* Bump PORTREVISIONS for ports depending on the canonical version of GCC andgerald2016-11-20