From owner-freebsd-ports@freebsd.org Sun Dec 24 05:46:05 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 508CDE9D229 for ; Sun, 24 Dec 2017 05:46:05 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0079569D21 for ; Sun, 24 Dec 2017 05:46:04 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-ua0-x22f.google.com with SMTP id f10so7882692ual.6 for ; Sat, 23 Dec 2017 21:46:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=fyiNBLth7SKBvhgYx/u6dQZF+jtzo/4++SpjzVmVn2c=; b=iP9y2oje80485FZ/09BH4klo0I64Uz8NOcnCbE1CMOXhH1gF1EVTYkAk4DSgm2YCLz tvnVANinEkjhbUuHMisqrHrIO3zEWAIfLCEUV5I3YpG1q/gQnV60hxzuz7xJqPGSKJNv sj/DL453Cb1Wkr/o67031zt7MY03SyTZi+Nhi/Uk11tleDO0d8qmA4eP0Q48Kz9kcyUn sDd7WHlbs36GKPtNk/U4SztFDsFLbvCsB8+BA9QvlFA6F5MTD+W98G+jyrYLjJqdAG+J RLil314vd1KXX7lyS/zxvuIltIDYQ7WO9O04OVUyblJMuvzV6ksh1Bl9R9l8WXorGGnq ZUcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=fyiNBLth7SKBvhgYx/u6dQZF+jtzo/4++SpjzVmVn2c=; b=XL++Q/iyTtmTn09ckjZa8wqZ5FhKHeg270MUcPOmntLa/LL5QqKZW7QA+2iOtWdRNE Sa0cATXm7FBJCs/tN2plMnafbs4McrNn45zY2Dqj3x6qsaoBZt6D20I84QLdn8mV7jY4 BcCX8G47srplH1GGMmCjJulB4gBGqCMssvf8HHpwMr826SsIs4kkk2GzPwmIqJyFzQAb nJeYmlSBtwyO37APICOh6Ty21KwpvYW8/IWsWkSgO0R+RLRILjMma6MkaFT7URy4FJaW PuGxZS7KKdjyBSBwgPc0jMSWWaaWb8TCgzuROUH0IlyOf9SXO2T7oOBOjCdpRDqCUi8B bkSQ== X-Gm-Message-State: AKGB3mLZBX9n18iQ5gGk0bHEtOxa7kLij+rd0BmkuTkONB1LnWtFXLdh FU9ks565x+MAoWOb97bFInmL2hEwNUGbl6f2VEY= X-Google-Smtp-Source: ACJfBotR+I7nglsiQO51pk1uizaZt22ZBHN2//kivdnkPEW5T10PPM4os+hPQKdD9Yt75P9mqUJJ4peSZ4djPHcKXqw= X-Received: by 10.176.12.24 with SMTP id a24mr2878272uak.128.1514094363891; Sat, 23 Dec 2017 21:46:03 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.147.156 with HTTP; Sat, 23 Dec 2017 21:46:03 -0800 (PST) In-Reply-To: <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> References: <5A39F7C9.1030800@grosbein.net> <05504d3c-3225-e83f-8f10-225319421a35@gmx.de> <5A3B7BFF.2020202@grosbein.net> <845b162a-918d-4a5f-c3c2-4f58b60bff73@gmx.de> <5A3CA1B5.2090907@grosbein.net> <1f5623f9-0ed1-3fb7-d81a-efd2f08ae3c8@gmx.de> From: Kevin Oberman Date: Sat, 23 Dec 2017 21:46:03 -0800 X-Google-Sender-Auth: 4JQtuT4EE6JYNj2G2kem216_zAQ Message-ID: Subject: Re: Procmail got updated! To: Matthias Andree Cc: FreeBSD Ports ML , Eugene Grosbein Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2017 05:46:05 -0000 On Sat, Dec 23, 2017 at 2:42 AM, Matthias Andree wrote: > Am 23.12.2017 um 08:12 schrieb Kevin Oberman: > > > > So, why does Eugene's question have no relevance to the procmail > > case? Could you please explain? > > Because I am not willing to discuss generics when we have a specific > case of port at hand. > The attempted generalization distracts from that, and I insinuate that > distraction is the purpose. > Everyone is free to start a new thread about general port maintenance > and removal principles > OK. I'm not sure this is in any way fair and not just avoidance, but why, specifically, should THIS port with no known vulnerabilities, people who are willing to work to fix it, and a fair number of users, be a so special that it deserves summary execution from FreeBSD? Yes, it's unmaintained. The upstream authors/maintainers advised a move to another port. But why should THIS port be removed from hte system? -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683