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. The most common
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. The most common
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
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
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,
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,
Quoting Chris Forgeron cforge...@acsi.ca (from Wed, 06 Oct 2010
11:45:03 -0300):
I'd like to step up and offer to modernize and maintain the ICC port
for FreeBSD.
I may be crazy, specially as 9 is going towards Clang/LLVM. With
that move, there may be a lot of very talented people
Hello,
I have several questions concerning creating Makefile
I don't understand in what sequence USE_* flags in Makefile are processed,
for example - in archives/jzlib/Makefile add
USE_APACHE=22, before
USE_JAVA=yes
USE_JAVA=1.4+
but when i execute make install, first install JAVA.
Is
Hello.
I've seen interesting commit message in postgresql90-server port: Also,
try to break the previous 1:1 relation between FreeBSD system and
PostgreSQL versions installed. Use different PREFIX:es to install
different versions on the same system.
I've fetched new version of ports and tried
Hi,
True, it is a first shot at breaking the 1:1 relationship, it is not a
solution. I think that if you install all PostgreSQL:s in different
PREFIXes, it will work to install them.
As you say, they should opimtally install in their own non-conflicting
places without changing prefix.
--On 7 oktober 2010 15.06.37 +0200 Palle Girgensohn gir...@freebsd.org
wrote:
Hi,
True, it is a first shot at breaking the 1:1 relationship, it is not a
solution. I think that if you install all PostgreSQL:s in different
PREFIXes, it will work to install them.
or if you install in prefix
Hello.
Just a notice. It seems it will not work to install different postgresql
versions in different PREFIX'es at least because of bsd.databases.mk:
lines 181 - 186: if we look at postgresql version in $LOCALBASE, it will
be different from one from $PREFIX.
Palle Girgensohn wrote:
True, it
Please see ports/150493 for someone who seems to be looking at it.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx
when it encounters a text/html file type. Instead it simply displays the raw
html text. According to their UPDATING file, they say:
all text/* parts can be displayed inline without mailcap
Which is suspiciously in
On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote:
The new version of mutt-devel nolonger honors my mailcap entry to invoke lynx
when it encounters a text/html file type. Instead it simply displays the raw
html text. According to their UPDATING file, they say:
all text/* parts
Chris Jones posted a pf action for fail2ban over a year ago with the
suggestion that it should be added to the official port. I've attached a
patch to include in the port which provides the bsd-pf action out of the
box.
Can this be included into the fail2ban port?
Regards
--
John Bayly
On Thu, Oct 07, 2010 at 06:51:38AM -0700, Jeremy Chadwick wrote:
On Thu, Oct 07, 2010 at 08:22:09AM -0500, Bob Willcox wrote:
The new version of mutt-devel nolonger honors my mailcap entry to invoke
lynx
when it encounters a text/html file type. Instead it simply displays the raw
html
I just want to report that it seems that portsnap5.FreeBSD.org is not
responding.
# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
Fetching snapshot tag from portsnap5.FreeBSD.org... failed.
...
___
What's holding it against updating to a more recent version, e.g 2.0.3?
Does any port depend on it, excluding fasl?
I want to convert stumpwm to bsd.cl-asdf.mk. In order to do it I need
textproc/cl-ppcre and x11/cl-clx ports. I've made a port for the latter.
However, stumpwm doesn't like the old
Hi,
I've seen the security alert for the current horde-base (3.3.8) port.
It looks like 3.3.9 was released just over a week ago, and the release
notes seem to indicate it fixes the security problems.
I also see http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/151191, but
I have no idea if that
On 07/10/2010 21:47:34, Harlan Stenn wrote:
Hi,
I've seen the security alert for the current horde-base (3.3.8) port.
It looks like 3.3.9 was released just over a week ago, and the release
notes seem to indicate it fixes the security problems.
I also see
Your mail to 'sage-members' with the subject
Mqdrrxknlafvix
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
Either the message will get posted to the list, or you will receive
notification of the
22 matches
Mail list logo
