Am 11.05.2012 04:42, schrieb Robert Simmons:
> And, this is the version of BerkeleyDB that it compiles and installs
> to satisfy the BDB backend that I enabled during config:
> db41-4.1.25_4
Try with the newest BDB that builds. Chances are versions 4.4 and beyond
are better-behaved, chances are t
2012/4/19 Alex Dupre :
>> FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
>> portstree. Thank you in advance.
>
> I'm just waiting for final release of suhosin (both patch and extension)
> to commit the update.
>
Do you know the release date of suhosin for this version? Stefan Es
On 5/11/12 2:12 PM, Svyatoslav Lempert wrote:
2012/4/19 Alex Dupre:
FreeBSD 8.3 is done, please commit update lang/php5 to PHP 5.4 to
portstree. Thank you in advance.
I'm just waiting for final release of suhosin (both patch and extension)
to commit the update.
Do you know the release date
Tested using xfcemerge; Thunar untested.
Great one-man-show!
2 tiny problems:
1. In bsd.xfce.mk, -L is a LDFLAGS, not CPPFLAGS. I saw too many clang
'unused option' warnings during the compilation;
2. The xfcemerge does not delete files. the files/ dir under
xfce4-systemload is removed, right?
O
Hi,
portmgr has been working for long on a new option framework for the ports to
improve some of the deficiencies in the current framework. The new framework
not only streamlines the current inconsistencies, but also adds new paradigms
like exclusive options, one-of-many, many-of-many, and mor
Hi all,
Please test:
# portsnap fetch -s geodns.portsnap.freebsd.org
If you experience any problems, please let me know where you are, which mirror
was selected, and what address `host -t a $mirror` returns for it. (As the
name suggests, different people should will get different mirrors.)
--
There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
or here:
dig +short @72.52.71.1 geodns.portsnap.freebsd.org A
dig +short @38.103.2.1 geodns.portsnap.freebsd.org A
dig +short @63.243.194.1 geodns.portsnap.freebsd.org A
Maybe this hasnt propogated yet ? or is it @ 127.0.0.1 ;)
O
On 05/11/12 21:54, Jason Hellenthal wrote:
> There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
There's not supposed to be an A record. Portsnap should work
anyway... it uses SRV. :-)
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author,
On Fri, May 11, 2012 at 09:55:13PM -0700, Colin Percival wrote:
> On 05/11/12 21:54, Jason Hellenthal wrote:
> > There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
>
> There's not supposed to be an A record. Portsnap should work
> anyway... it uses SRV. :-)
Aaah! you got me ther
On 5/12/2012 1:13 AM, Jason Hellenthal wrote:
>
> On Fri, May 11, 2012 at 09:55:13PM -0700, Colin Percival wrote:
>> > On 05/11/12 21:54, Jason Hellenthal wrote:
>>> > > There is no A record @8.8.8.8 or @8.8.4.4 or at the root servers.
>> >
>> > There's not supposed to be an A record. Portsnap
Erwin Lansing ha scritto:
portmgr has been working for long on a new option framework for the ports to
improve some of the deficiencies in the current framework.
Great work! Looking quickly at the documentation I have a doubt: while I
think most ports handle NOPORTDOCS, I think WITHOUT_NLS is
11 matches
Mail list logo
