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
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
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 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 probl
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 probl
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I am launching an initiative to give the community the opportunity to
fund further development on portmaster. As much as I love doing this
work I need to be able to support myself and my family and the kinds
of features that users have requested (
Hello,
I discovered a strange problem with the FreeBSD port of OCaml.
Frama-C/Jessie is a formal verification framework for C code, written in
OCaml. The Beryllium distribution [1] compiles on OpenBSD, NetBSD, and
Linux, but not on FreeBSD. On FreeBSD 7.2, I tried OCaml 3.11.0 as well as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We're happy to announce that KDE-4.3.2 is ready
for testing. KDE-4.3.2 is only a Bugfix release.
If you want to play with KDE 4.3.2 please checkout
all ports from area51.
A note about area51, we have changed the repo layout,
Qt and KDE is now split be
On Fri, Oct 2, 2009 at 10:32 AM, Dmitry Marakasov wrote:
> * Mark Linimon (lini...@lonesome.com) wrote:
>
>> The author orginally contacted us with a legal threat because we were
>> not in compliance with the 28-day clause. A long, acrimonious disucssion
>> ensued. In that discussion, the author
On Mon, Oct 05, 2009 at 09:38:51PM -0400, B. Cook wrote:
> Hello all,
>
> Strange thing going on w/ adzap.. possible problem on the server?
>
> Seems as if md5/sha256 doesn't match.. but the size is right.
I'm using adzap extensively at home and at work, so I'm quite
interested in solving this p
Thank a lot you for clarification!
2009/10/6 Mark Linimon
> On Tue, Oct 06, 2009 at 12:06:08PM +0400, Alexander Bubnov wrote:
> > Why FreeBSD does not use pkgsrc of NetBSD project as default ports?
>
> You're able to do so if you like -- FreeBSD is a supported pkgsrc
> platform IIUC.
>
> OTOH, t
> You're blocking mail from FreeBSD.org, among others:
>
> : host mail.kr.freebsd.org[210.118.94.73] said: 554
> Service unavailable; Client host [69.147.83.53] blocked using krrbl.or.kr
> (in reply to RCPT TO command)
>
> mcl
FYI
69.147.83.5 is in one of yahoo's IP blocks
David
__
On Tue, Oct 06, 2009 at 12:06:08PM +0400, Alexander Bubnov wrote:
> Why FreeBSD does not use pkgsrc of NetBSD project as default ports?
You're able to do so if you like -- FreeBSD is a supported pkgsrc
platform IIUC.
OTOH, there are some things FreeBSD ports are able to do that pkgsrc
can't (e.g.
Hello everybody!
Probably I am going to ask a stupid question but it is very interesting for
me. Because I would like to help BSD projects.
Why FreeBSD does not use pkgsrc of NetBSD project as default ports? I guess
work can be faster in case port system is shared between BSD projects
including Op
15 matches
Mail list logo