PHP version retirement

2019-08-10 Thread Martin Waschbüsch
Hi all, At least the last two versions of PHP, 5.6 & 7.0, were removed from ports as soon as (or even shortly before) they were no longer actively maintained upstream. I am unsure what the exact reasoning behind this was, but I do not think it is a good idea moving forward: I suppose it is tr

Re: PHP version retirement

2019-08-10 Thread Carmel NY
On Sat, 10 Aug 2019 10:17:44 +0200, Martin Waschbüsch stated: >Hi all, > >At least the last two versions of PHP, 5.6 & 7.0, were removed from >ports as soon as (or even shortly before) they were no longer actively >maintained upstream. I am unsure what the exact reasoning behind this >was, but I d

Re: PHP version retirement

2019-08-10 Thread Kurt Jaeger
Hi! [...] > Would it not be better to have, say, the last two versions before > current stable still in ports but with a huge disclaimer saying: > use at your own risk, etc.? > > What do y'all think? You make the case for something other systems call backports, basically, keeping stuff in workin

Any alternatives to NONE cipher ssh or bbcp for gigabit+ zfs

2019-08-10 Thread Ash Gokhale
I wrote viamillipede exactly for this eventuality. It's a resilient pipe to socket multiplexer for high throughput and can use mulitple l1,l2, l3 network paths. The initial version is in ports at net/viamillipede or you can follow the dev line : https://github.com/agokhale/viamillipede

Re: PHP version retirement

2019-08-10 Thread Patrick Powell
On 2019-08-10 01:17, Martin Waschbüsch wrote: Hi all, At least the last two versions of PHP, 5.6 & 7.0, were removed from ports as soon as (or even shortly before) they were no longer actively maintained upstream. I am unsure what the exact reasoning behind this was, but I do not think it is

Re: PHP version retirement

2019-08-10 Thread Martin Waschbüsch
> Am 10.08.2019 um 12:53 schrieb Carmel NY : > > On Sat, 10 Aug 2019 10:17:44 +0200, Martin Waschbüsch stated: >> Would it not be better to have, say, the last two versions before >> current stable still in ports but with a huge disclaimer saying: use >> at your own risk, etc.? >> >> What do y'a

Re: PHP version retirement

2019-08-10 Thread Martin Waschbüsch
> Am 10.08.2019 um 20:18 schrieb Patrick Powell : > > Umm this was just the kick in the pants that I needed to switch to PHP 7. > See https://www.glaver.org/blog/?p=1109 for a desperation 'I need PHP5.6' > hack which I used during this update. Thank you, Patrick, that is a work-around I also c

Re: PHP version retirement

2019-08-10 Thread Wolfgang Zenker
* Martin Waschbüsch [190811 00:47]: >> Am 10.08.2019 um 20:18 schrieb Patrick Powell : >> >> Umm this was just the kick in the pants that I needed to switch to PHP 7. >> See https://www.glaver.org/blog/?p=1109 for a desperation 'I need PHP5.6' >> hack which I used during this update. > Thank yo

[NEW PORT] net-p2p/lidarr: Music collection manager for Usenet and BitTorrent users

2019-08-10 Thread Matt Russi
Hi all, My apologies if this is not the correct place to post this. Would a committer be available to review this New Port request? portlint and testport are OK. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234233 Regards, Matt ___ freebsd-ports@f