Re: curl 7.48.0 does not build with libressl 2.2.6

2016-03-28 Thread Ryan Schmidt
> On Mar 28, 2016, at 10:39 PM, Kastus Shchuka wrote: > > >> On Mar 28, 2016, at 7:47 PM, Ryan Schmidt wrote: >> >> >> On Mar 28, 2016, at 4:36 PM, Kastus Shchuka wrote: >> >>> I understand that I am dealing with a non-standared configuration of >>> macports >>> as I use libressl instead o

Re: curl 7.48.0 does not build with libressl 2.2.6

2016-03-28 Thread Kastus Shchuka
> On Mar 28, 2016, at 7:47 PM, Ryan Schmidt wrote: > > > On Mar 28, 2016, at 4:36 PM, Kastus Shchuka wrote: > >> I understand that I am dealing with a non-standared configuration of macports >> as I use libressl instead of openssl, but still I think it's worth reporting >> the issue here. >>

Re: curl 7.48.0 does not build with libressl 2.2.6

2016-03-28 Thread Ryan Schmidt
On Mar 28, 2016, at 4:36 PM, Kastus Shchuka wrote: > I understand that I am dealing with a non-standared configuration of macports > as I use libressl instead of openssl, but still I think it's worth reporting > the issue here. > > Let me first state that curl 7.47.1 port compiled and installed

curl 7.48.0 does not build with libressl 2.2.6

2016-03-28 Thread Kastus Shchuka
Hi, I understand that I am dealing with a non-standared configuration of macports as I use libressl instead of openssl, but still I think it's worth reporting the issue here. Let me first state that curl 7.47.1 port compiled and installed just fine previously with libressl 2.2.6 (current macports

dovecot2-antispam update?

2016-03-28 Thread Terry Barnum
I updated dovecot2 from 2.2.19_1 to 2.2.22_0 but had to back out because of errors about dovecot2-antispam 0.0-51_12 ABI being incompatible. Will dovecot2-antispam be updated or is there a workaround? > Mar 21 14:05:31 mail dovecot[16635]: imap(u...@domain.com): Error: Couldn't > load required

Re: MKVmerge incompatible version?

2016-03-28 Thread Ryan Schmidt
> On Mar 27, 2016, at 8:11 PM, [ftp83plus] wrote: > > Hello all, > > I installed MKVToolnix from MacPorts on my 10.6.8. However it reports an > error on launch: > >> L'interface est configurée pour fonctionner avec un exécutable mkvmerge >> d'une version différente () de la sienne (mkvmerge

Re: python_select

2016-03-28 Thread Joshua Root
If you want to run 'python', use python_select. This can be linked to any version of python. If you want to run 'python2' or 'python3', use the others. These can only be linked to python 2.x or 3.x respectively. A common use for this might be if you have scripts that only work with one or the o

Re: python_select

2016-03-28 Thread Mark Brethen
So if you have a single python version installed use python_select, whereas python2_select and python3_select allow you to set those default versions if you need both? > On Mar 28, 2016, at 5:46 AM, Joshua Root wrote: > > Mark Brethen wrote: >> Why are there a python_select, python2_select and

python_select

2016-03-28 Thread Joshua Root
Mark Brethen wrote: Why are there a python_select, python2_select and python3_select? When is one vs the others used? They allow creating links 'python', 'python2' and 'python3' respectively. - Josh ___ macports-users mailing list macports-users@lis

py-pip usage

2016-03-28 Thread Joshua Root
Mark Brethen wrote: How is the py-pip port used to install python packages and where are they installed? Is this advisable? You use it just as described in the pip documentation[1]. By default the packages go to the same place as a normal distutils install, which is not a good idea since tha