On Wed, 17 Jan 2007 01:04:05 +0100
Pav Lucistnik <[EMAIL PROTECTED]> wrote:
> Gabor Kovesdan píše v út 16. 01. 2007 v 18:26 +0100:
> > Joe Holden schrieb:
> > > Does anyone know why this is the case? It builds and installs fine on
> > > my machines. If its just a port conflict, surely just addin
> > > And one that is supposed tofix the issue:
> > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/103861
> > >
> > > As it is a big change, that affects about 40 port, it needs
> > > test/approval from the Ports Management Team. I put them into CC, maybe
> > > they can give you more informa
Gabor Kovesdan píše v út 16. 01. 2007 v 18:26 +0100:
> Joe Holden schrieb:
> > Does anyone know why this is the case? It builds and installs fine on
> > my machines. If its just a port conflict, surely just adding
> > CONFLICTS to the makefiles of both libnet ports etc would do the trick?
> >
>
Joe Holden schrieb:
Does anyone know why this is the case? It builds and installs fine on
my machines. If its just a port conflict, surely just adding
CONFLICTS to the makefiles of both libnet ports etc would do the trick?
Or is there another reason?
It seems there is a long-standing issue w
Does anyone know why this is the case? It builds and installs fine on my
machines. If its just a port conflict, surely just adding CONFLICTS to
the makefiles of both libnet ports etc would do the trick?
Or is there another reason?
Ta,
Joe
___
freebs
