Number of commits found: 32

Mark as broken on aarch64: fails to link with sbrk.

While here, pet portlint and remove stale ia64 lines.

Approved by:	portmgr (tier-2 blanket)

Remove NLS, DOCS, EXAMPLES and IPV6 from OPTIONS_DEFAULT, they are enabled by
default anyway and don't need to be listed

Approved by:	portmgr blanket

irc/irc: convert to CONFIGURE_OUTSOURCE

Approved by:	portmgr blanket
Differential Revision:	https://reviews.freebsd.org/D5818

The IRC configure script has curious logic, is being overly complex,
and actually breaks badly if the port is being built in a chroot
where the host triplet won't match the jail triplet.

The solution I've provided here is clean.  Using the pre-configure
target, the build directory (with a fixed name) is created and the
needed configure script and header are copied over, just like the top
configure script does.  Then the port makefile just configures with
that.  It's much better, more robust, and fixes the triplet mismatch.

PR:		194679
Submitted by:	marino

Convert all :U to :tu and :L to :tl

Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)

bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore

Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier

With hat:	portmgr

Enable stage support

Add NO_STAGE all over the place in preparation for the staging support (cat:
irc)

irc/irc: Replace hardcoded "freebsd" with OPSYS:L

Using OPSYS allows the port to build on DragonFly without modification.
The header was also trimmed, but there was no function change made to the port.

Approved by:	bapt/culot (mentors, implicit)

Move the rc.d scripts of the form *.sh.in to *.in

Where necessary add $FreeBSD$ to the file

No PORTREVISION bump necessary because this is a no-op

- Register conflicts with other IRC servers[1]
- Convert to new options framework

Submitted by:   Sulev-Madis 'ketas' Silber <madis555@hot.ee> [1]

Update to irc 2.11.2p3 (bugfix release)

Update my mail address to @FreeBSD.org

Feature safe:   yes

Update to 2.11.2p2

Update to 2.11.2p1 (bugfix release)

- Update to 2.11.2
- Simplify Makefile
- Claim maintainership

- Remove FreeBSD 4.X support from unmaintained ports in categories starting
  with letter i-m

- Update to 2.11.1p1

PR:             ports/83176
Submitted by:   Krzysztof Kowalik <kkowalik+pr@uci.agh.edu.pl>

Update to version 2.11.1.

PR:             ports/81626
Submitted by:   Johan van Selst

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

- Update to 2.11.0

PR:             ports/78073
Submitted by:   Sam Lawrance <boris@brooknet.com.au>

fix build for gcc 3.4.2
remove BROKEN

BROKEN on 5.x: Does not compile with gcc 3.4.2

- Update to 2.10.3p6

PR:             ports/64553
Submitted by:   Paolo Gatti <onel0ve@softhome.net>

freebsd port update: irc/irc to 2.10.3p5

Submitted by:   Eugene <eugene3@web.de> (via private email)

- ECHO -> ECHO_MSG

for some ports:
- pre-fetch -> pre-everything

PR:             ports/56785-56799
Submitted by:   KATO Tsuguru <tkato@prontomail.com>

update irc/irc: 2.10.3 -> 2.10.3p3

PR:             55824
Submitted by:   Paolo Gatti <onel0ve@libero.it>

De-pkg-comment.

Fix PORTCOMMENTs that were killing INDEX builds.

105 pointy hats to:     me
Approved by:            pat

Remove jseger and torstenb from maintainership of their ports, they   have been
inactive for too long    

Fix %%PREFIX%% in ${PREFIX}/etc/rc.d/ircd.sh startup script.    

As threatened on freebsd-ports: all startup scripts know about the two   options
`start' and `stop' now (unless I have forgotten any). This allows   us to call
the scripts from /etc/rc.shutdown with the correct option.    

Number of commits found: 32

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

^* - modified, not new

All vulnerabilities

Last updated:
2019-09-14 22:19:58