3 ms·
Not true any longer, at least for the binary packages I produce[0]. I switched them over to trunk-based builds a while ago, which are updated every few days.
by jperkin 10y ago
Not true any longer, at least for the binary packages I produce[0]. I switched them over to trunk-based builds a while ago, which are updated every few days.
[0] https://pkgsrc.joyent.com/install-on-osx/ https://pkgsrc.joyent.com/install-on-osx/
- mseri 10y agoHow is situation with python3 on osx? Last time I used pkgin, it was not compiled as Framework preventing some libraries to work properly
- jperkin 10y agoThey're all available: $ pkgin se python3 python35-3.5.1nb2 Interpreted, interactive, object-oriented programming language python34-3.4.4 Interpreted, interactive, object-oriented programming language python33-3.3.6nb3 Interpreted, interactive, object-oriented programming language along with a bunch of pre-packaged modules: $ pkgin avail | grep ^py3 | wc -l 1412 Let me know if anything you need is missing and I'll add it.
- mseri 10y agoThanks. I had to look back at my notes. I had issues with matplotlib and few other packages at the time with python 3.4, due to python not being built as framework. I have just found a related issue: https://github.com/joyent/pkgsrc/issues/331 https://github.com/joyent/pkgsrc/issues/331 Unfortunately, from what I read there, I have still to use homebrew or install from python.org (with those I have no issue). I really enjoyed pkgin otherwise.