Number of commits found: 8

- Fix 'make index' when system is built with WITHOUT_PORTSNAP by
  falling back on the perl make_index if needed.

With hat:	portmgr
Reported by:	ade

Use the portsnap version of make_index instead of the perl version.

Submitted by:	ak

Major optimizations for 'make index' and other recursive traversal
targets.

* Use /rescue/sh for index builds instead of /bin/sh, when it exists.
  The former is statically linked and faster to execute, which becomes
  significant when executing it tens of thousands of times.  This
  trick can be used with other recursive targets by passing in
  __MAKE_SHELL.

* Get rid of make variable assignments that use != command invocations
  in the critical path, using several methods:

  - rewriting logic to use shell or make builtins instead of external command
executions
  - macroizing commands and executing them in the targets where they
    are needed instead of with every invocation of make

(Only the first 15 lines of the commit message are shown above )

Fix bogus comments.  No code change.

Remove traling spaces.

* Be even more explicit about partial ports trees being unsupported
  for INDEX builds [1]

* Remove the parallel target from Makefile; this is heavily tied to
  the package build cluster and can be better done in the makeparallel
  script (commit to follow) [2]

* Extend the format of INDEX to separately list the
  EXTRACT/PATCH/FETCH_DEPENDS instead of lumping them all in together
  with BUILD_DEPENDS.  The three new fields are appended to the end of
  the record in that order. [2]

* Change BROKEN to IGNORE in BROKEN_WITH_MYSQL failure code [3]

* Support non-default PREFIX for perl 5.00503 [5]

(Only the first 15 lines of the commit message are shown above )

Do a better job of stating which port we had problems with while
mapping directories to package names.

Check for duplicate entries in INDEX and warn about them.

Submitted by:   Martin Heinen <martin@sumuk.de>
PR:             ports/33196 (based on)

Number of commits found: 8

7 vulnerabilities affecting 113 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2019-05-25 23:10:02