Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

On Sun, 3 Feb 2019, Bill Cole wrote: http://www.cvedetails.com/vendor/225/Procmail.html makes interesting reading, as does any search for "procmail CVE". Perhaps it's just me, but I don't think insecure software belongs in MacPorts unless someone is willing to fix it (and good luck with

Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

On 2 Feb 2019, at 20:59, Dave Horsfall wrote: On Sun, 3 Feb 2019, Joshua Root wrote: No official policy. My view is that the only clear-cut case is when a port doesn't build or work at all, anywhere, and there's no real chance of that ever changing. How about insecure ports such as

Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

Dave Horsfall wrote: > On Sun, 3 Feb 2019, Joshua Root wrote: > > > No official policy. My view is that the only clear-cut case is when a > > port doesn't build or work at all, anywhere, and there's no real chance > > of that ever changing. > > How about insecure ports such as Procmail? It's a

Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

How about maildrop? Nothing I know of (except procmail) will use existing .procmailrc files, but e.g. http://www.wonkity.com/~wblock/docs/html/maildrop.html shows some examples of migrating (e.g. sendmail configuration, some .procmailrc

Re: [macports-ports] branch master updated: nrpe, nsca: remove outdated ports

On Sun, 3 Feb 2019, Joshua Root wrote: No official policy. My view is that the only clear-cut case is when a port doesn't build or work at all, anywhere, and there's no real chance of that ever changing. How about insecure ports such as Procmail? It's a scripting language, with Shell