| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Bump PORTREVISION for ports depending on the canonical version of GCC | Gerald Pfeifer | 2018-12-12 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | | | | defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t GCC 8.2 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, c11, c++0x, c++11-lang, c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib plus, as a double check, everything INDEX-11 showed depending on lang/gcc7. PR: 231590 Notes: svn path=/head/; revision=487272 | ||||
| * | databases/pgsanity: Update to 0.2.9 | Danilo G. Baio | 2018-03-20 | 2 | -5/+4 |
| | | | | | | | | | PR: 226730 Submitted by: Mateusz Piotrowski <0mp@FreeBSD.org> (maintainer) Notes: svn path=/head/; revision=465138 | ||||
| * | New port: databases/pgsanity | Tobias Kortkamp | 2018-03-18 | 3 | -0/+52 |
| PgSanity checks the syntax of PostgreSQL SQL files. It does this by leveraging the ecpg command which is traditionally used for preparing C files with embedded SQL for compilation. However, as part of that preparation, ecpg checks the embedded SQL statements for syntax errors using the exact same parser that is in PostgreSQL. So the approach that PgSanity takes is to take a file that has a list of bare SQL in it, make that file look like a C file with embedded SQL, run it through ecpg and let ecpg report on the syntax errors of the SQL. WWW: https://github.com/markdrago/pgsanity PR: 226689 Submitted by: 0mp Notes: svn path=/head/; revision=464904 | |||||
 |
index : ports | |
| FreeBSD ports tree |
| aboutsummaryrefslogtreecommitdiff |