On Thu, Apr 09, 2015 at 01:59:42PM +0200, Christian Weisgerber wrote:
Bryan Drewery:
Are you mixing ports and packages?
No. Ports only.
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports only you have to be
On Thu, Apr 09, 2015 at 05:53:45PM +0200, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports only you have to be
extra
careful, (same goes with ncurses or ports
On 04/09/2015 11:53, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports only you have to be
extra
careful, (same goes with ncurses or ports openssl) just installing
On 09 Apr 2015, at 19:33, Adam McDougall mcdou...@egr.msu.edu wrote:
On 04/09/2015 11:53, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports only you have to be
On 4/9/2015 11:14 AM, Baptiste Daroussin wrote:
On Thu, Apr 09, 2015 at 04:00:45PM +, Loganaden Velvindron wrote:
On Thu, Apr 9, 2015 at 3:56 PM, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Apr 09, 2015 at 05:53:45PM +0200, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how
On Thu, 9 Apr 2015, Matthew Seaman wrote:
On 04/09/15 17:14, Baptiste Daroussin wrote:
For now candidates are:
libarchive
ncurses
readline (which will have then to be linked to ports ncurses and not base
version through the magic of fake libtermcap)
openssl
libedit(?)
One I noticed recently
Baptiste Daroussin:
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports only you have to be extra
careful, (same goes with ncurses or ports openssl) just installing those ports
is enough to pollute nearly anything you
On Thu, Apr 09, 2015 at 04:00:45PM +, Loganaden Velvindron wrote:
On Thu, Apr 9, 2015 at 3:56 PM, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Apr 09, 2015 at 05:53:45PM +0200, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how you have mixed up things between base
On 04/09/15 17:14, Baptiste Daroussin wrote:
For now candidates are:
libarchive
ncurses
readline (which will have then to be linked to ports ncurses and not base
version through the magic of fake libtermcap)
openssl
libedit(?)
One I noticed recently was in ftp/curl -- if you're using the
Bryan Drewery:
Are you mixing ports and packages?
No. Ports only.
--
Christian naddy Weisgerber na...@mips.inka.de
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Thu, Apr 9, 2015 at 3:56 PM, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Apr 09, 2015 at 05:53:45PM +0200, Christian Weisgerber wrote:
Baptiste Daroussin:
Some how you have mixed up things between base openssl and libressl, when
starting to activate libressl if you are using ports
On 4/8/2015 2:56 PM, Christian Weisgerber wrote:
It looks like our already complicated situation with base OpenSSL
and ports OpenSSL got even messier with the addition of LibreSSL.
I recently installed security/libressl for the pending net/openntpd
update (*). Now when I try to pkg delete it
It looks like our already complicated situation with base OpenSSL
and ports OpenSSL got even messier with the addition of LibreSSL.
I recently installed security/libressl for the pending net/openntpd
update (*). Now when I try to pkg delete it again, I get this:
Installed packages to be REMOVED:
13 matches
Mail list logo
