Number of commits found: 13

* Updated to 20170630
* New maintainer Jov <amutu@amutu.com>

PR:		220445
Submitted by:	Jov <amutu@amutu.com> (maintainer)
Reviewed by:	lifanov (mentor)
Approved by:	lifanov (mentor)
Differential Revision:	https://reviews.freebsd.org/D11500

devel/google-styleguide: Save from expiration

- switch to GitHub
- use date-based version numbers
- set licenses
- install xml descriptions of style guides
- install files for editor integration
- install optional documentation
- add pkg-plist

Reviewed by:	mat
Approved by:	swills (mentor, implicit)
Differential Revision:	https://reviews.freebsd.org/D10141

Mark the remaining ports depending on Google Code as DEPRECATED, with an
EXPIRATION_DATE at the end of April 2017.

In the past six months, about a third of the ports marked BROKEN because
they were hosted on Google Code have been fixed.  The remaining must not
be of use to anyone.

With hat:	portmgr
Sponsored by:	Absolight

leeym handed in his commit bit.

GOOGLE_CODE has gone away.

- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN

Some ports have a local mirror configured but for security reasons, it
is not considered upstream.

Sponsored by:	Absolight

- Convert ports of devel/ to USES=python

Approved by:	portmgr (implicit)

Remove indefinite articles and trailing periods from COMMENT, plus
minor COMMENT typos and surrounding whitespace fixes. Categories D-F.

CR:		D196
Approved by:	portmgr (bapt)

- Support staging
- Define DOCS option

Add NO_STAGE all over the place in preparation for the staging support (cat:
devel part 2)

- update DIST_SUBDIR to copy files from correct path

Noticed by:     pav
Feature safe:   yes

- utilize DIST_SUBDIR to solve distfiles conflict

Suggested by:   vanilla
Feature safe:   yes

- update to Revision 66 and unbreak it

Noticed by:     erwin
Feature safe:   yes

- add google-styleguide 52

This is automated checker to make sure a C++ file follows Google's C++ style
guide (http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml). As it
heavily relies on regular expressions, cpplint.py won't catch all violations of
the style guide and will very occasionally report a false positive. There is a
list of things we currently don't handle very well at the top of cpplint.py,
and we welcome patches to improve it.

WWW: http://code.google.com/p/google-styleguide/

Number of commits found: 13

14 vulnerabilities affecting 129 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2018-04-26 12:01:18