From owner-freebsd-ports@FreeBSD.ORG Wed Sep 7 06:51:47 2011 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5524F1065672 for ; Wed, 7 Sep 2011 06:51:47 +0000 (UTC) (envelope-from erwin@FreeBSD.org) Received: from vocal.dk-hostmaster.dk (vocal.dk-hostmaster.dk [193.163.102.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0F7908FC0A for ; Wed, 7 Sep 2011 06:51:46 +0000 (UTC) Received: from ekko.dkhm (ekko.dkhm [172.16.1.61]) by vocal.dk-hostmaster.dk (Postfix) with ESMTP id 35EB330BA8; Wed, 7 Sep 2011 08:33:24 +0200 (CEST) Received: from dhcp-125.dkhm (dhcp-125.dkhm [172.16.1.125]) by ekko.dkhm (8.14.2/8.14.2) with ESMTP id p876XMxN018896; Wed, 7 Sep 2011 08:33:22 +0200 (CEST) (envelope-from erwin@FreeBSD.org) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Erwin Lansing In-Reply-To: <20110906233004.f0a93ac6.stas@FreeBSD.org> Date: Wed, 7 Sep 2011 08:33:22 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <2E6619D2-634B-46CA-82F1-EBEA3DB593E9@FreeBSD.org> References: <20110904231821.GC22986@lonesome.com> <201109051005.p85A5ZvN005263@fire.js.berklix.net> <20110906233004.f0a93ac6.stas@FreeBSD.org> To: Stanislav Sedov X-Mailer: Apple Mail (2.1244.3) Cc: ports@FreeBSD.org, Mark Linimon , "Julian H. Stacey" , portmgr@FreeBSD.org Subject: Re: sysutils/cfs X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2011 06:51:47 -0000 On Sep 7, 2011, at 8:30 AM, Stanislav Sedov wrote: > On Mon, 05 Sep 2011 12:05:35 +0200 > "Julian H. Stacey" mentioned: >=20 >> Mark Linimon wrote: >>> On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote: >>>> It is not responsible to threaten to remove ports without warning >>>> between releases for non urgent reasons. >>>=20 >>> portmgr has no such policy. >>>=20 >>> Ports get deleted all the time due to various issues. I prefer to = see >>> a 1- or 2-month warning via EXPIRATION_DATE, but that's my personal >>> preference, not a written policy. >>>=20 >>> mcl >>=20 >> Drive by ports shootings are becoming too frequent, & will get >> FreeBSD a bad name as immature & poorly managed >> A solution: Ensure a policy of expiry dates expire a release after >> a warning is given in a previous releases (except in emergency). >>=20 >=20 > I second this opinion. > We might have not needed the policy a while ago when such deprecations > were rare. Given that we gained several people working actively > on this I'd like to see some policy regarding deprecation as well. > I saw several occasions when ports were deprecated for no apparent > reason, so I can understand Julian and other people dissatisfaction > with this. >=20 > What about requiring that the ports deprecated should be either broken > or have known published vulnerabilties for a long period of > time (say 6 months) for the start? Personally, I'd also love to see > people deprecating ports provide a clear reasoning for deprecation in > the commit message (not just "deprecated some old ports" etc), so one > won't need to guess if he would like to fix/resurrect the port in the > feature? Portmgr is aware of the current discussion and will handle it in due = time. Thank you for bringing it to our attention. -erwin=