As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
lini...@freebsd.org wrote:
Subject:Re: FreeBSD unmaintained ports which are currently marked broken
I added cc: m...@freebsd.org FYI as creator of Makefile
> As part of an ongoing effort to reduce the number of problems in
> portname: comms/seyon
> broken because: Unfetchabl
lini...@freebsd.org wrote:
cc'd chinsan...@gmail.com as original creator of Makefile as
MAINTAINER= ports@
> As part of an ongoing effort to reduce the number of problems in
> portname: graphics/epdfview
> broken because: No public distfiles
> build errors: none.
> overvie
