/x11-themes/cursor-ecliz/

2018-03-12T19:20:32+00:00

fernape fernape@FreeBSD.org

2018-03-12T19:20:32+00:00

0b7279a4a556b3b591ca68bf31396dc2c685ba9c

Update MAINTAINER email address for Fernando Apesteguia from fernando.apesteguia@gmail.com Approved by: tcberner (mentor) Differential Revision: https://reviews.freebsd.org/D14668

Update MAINTAINER email address for Fernando Apesteguia
from fernando.apesteguia@gmail.com

Approved by:	tcberner (mentor)
Differential Revision:	https://reviews.freebsd.org/D14668

Unbreak the build against recent Clang. 2018-02-02T09:48:48+00:00 danfe danfe@FreeBSD.org 2018-02-02T09:48:48+00:00 9a716820d343ad7cecbf732651e0083b0582acd3 PR: 225538

PR:	225538

Bump PORTREVISION for ports depending on the canonical version of GCC 2017-09-10T20:55:38+00:00 gerald gerald@FreeBSD.org 2017-09-10T20:55:38+00:00 a8659f2c3a739594f865ddb2381c38d14c4d611e (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

(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

cad/stepcode: Fix portlint issues 2017-08-29T19:36:16+00:00 pi pi@FreeBSD.org 2017-08-29T19:36:16+00:00 4cc02130153ec01cd1ac8edd86e76484e927b12f PR: 221835 Submitted by: Fernando Apesteguia <fernando.apesteguia@gmail.com> (maintainer) MFH: 2017Q3

PR:		221835
Submitted by:	Fernando Apesteguia <fernando.apesteguia@gmail.com> (maintainer)
MFH:		2017Q3

Mark some ports failing on power64. In cases where the error message 2017-05-21T21:55:08+00:00 linimon linimon@FreeBSD.org 2017-05-21T21:55:08+00:00 46cb2aeb8c975eed72a92e539d1f62fc8f03beaf was a stub, provide a real one. While here, pet portlint. Approved by: portmgr (tier-2 blanket) Reported by: swills

was a stub, provide a real one.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)
Reported by:	swills

Bump PORTREVISIONs for ports depending on the canonical version of GCC and 2017-04-01T15:23:30+00:00 gerald gerald@FreeBSD.org 2017-04-01T15:23:30+00:00 8047a240e1cbbe6481930d3ec780c9c92fccd00c 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

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

In April/May 2012, STEP Class Library was renamed to STEPcode. This was done 2015-07-03T14:45:40+00:00 amdmi3 amdmi3@FreeBSD.org 2015-07-03T14:45:40+00:00 1df1f0fceb8594671aa80477d4aa7e3f0924079b because the old name wasn't accurate - the class libraries are only a fraction of the software. The STEP Class Library (SCL) originated at the National Institute of Standards and Technology, or NIST. NIST started working with STEP in the 80's and continued until the late 90's. Some components of SCL were originally written in Lisp and then re-written in mixed C and C++ in the early 90's. The rest of SCL was written in C++ to begin with. STEPcode (SC) includes the class libraries, some of the most widely used EXPRESS schemas, some tools to work with EXPRESS, and support libraries for those tools. Two of the tools can create schema-specific libraries that are used with the class libraries. There are also some test files and programs. WWW: https://github.com/stepcode/stepcode/wiki PR: 201046 Submitted by: fernando.apesteguia@gmail.com

because the old name wasn't accurate - the class libraries are only a fraction
of the software.

The STEP Class Library (SCL) originated at the National Institute of Standards
and Technology, or NIST. NIST started working with STEP in the 80's and
continued until the late 90's. Some components of SCL were originally written
in Lisp and then re-written in mixed C and C++ in the early 90's.
The rest of SCL was written in C++ to begin with.

STEPcode (SC) includes the class libraries, some of the most widely used EXPRESS
schemas, some tools to work with EXPRESS, and support libraries for those tools.
Two of the tools can create schema-specific libraries that are used with the
class libraries. There are also some test files and programs.

WWW: https://github.com/stepcode/stepcode/wiki

PR:		201046
Submitted by:	fernando.apesteguia@gmail.com