Re: portsnap not honoring WORKDIR and PORTSDIR?

On Sat, 21 Apr 2018 16:49:13 -0600 Gary Aitken wrote: > Is portsnap supposed to honor WORKDIR and PORTSDIR? > > These are defined in /etc/portsnap.conf, and it's not clear to me > whether they are honored only via the .conf file or whether they > are supposed to be honored from the environment

portsnap not honoring WORKDIR and PORTSDIR?

Is portsnap supposed to honor WORKDIR and PORTSDIR? These are defined in /etc/portsnap.conf, and it's not clear to me whether they are honored only via the .conf file or whether they are supposed to be honored from the environment as well. They appear to not be honored from the environment, and

Re: Committing ${name}_limits patches for the rc files of various databases

Hi! On Sat, 21 Apr 2018 20:44:05 +0200 Kirill Ponomarev wrote: >On 04/21, Mateusz Piotrowski wrote: >> Some of the patches were already incorporated into the ports tree, >> but many of them are still waiting to be committed. Recently, an >> update to database/mongodb36 was

Re: Committing ${name}_limits patches for the rc files of various databases

On 04/21, Mateusz Piotrowski wrote: > Hello, > > A few weeks ago I discovered a regression caused by the standardization > of the mechanism used to limit daemons resources with limits(1). This > feature was introduced in r328331[1]. Basically, it defines that > limits(1) could be controlled via

Re: Changing PHP default version from 5.6 to 7.2 timeframe?

[Default] On Thu, 19 Apr 2018 16:48:40 +0200, Kurt Jaeger wrote: >Hi! > >> It appears that there is some work going on to prepare to switch >> the default PHP version from 5.6 to an actively supported version. > >Yes. > >> What is the approximate timeframe for that change, if

Committing ${name}_limits patches for the rc files of various databases

Hello, A few weeks ago I discovered a regression caused by the standardization of the mechanism used to limit daemons resources with limits(1). This feature was introduced in r328331[1]. Basically, it defines that limits(1) could be controlled via rc.conf(5) using ${name}_limits variables as