From owner-freebsd-ports@freebsd.org Thu Sep 29 21:11:08 2016 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 40CD3C02BA0 for ; Thu, 29 Sep 2016 21:11:08 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8FEEC6D; Thu, 29 Sep 2016 21:11:07 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (pD9FE9EC2.dip0.t-ipconnect.de [217.254.158.194]) (authenticated bits=128) by land.berklix.org (8.15.2/8.15.2) with ESMTPA id u8TLAtpY020689; Thu, 29 Sep 2016 21:10:55 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id u8TLAsTH050093; Thu, 29 Sep 2016 23:10:54 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id u8TLAHgM037995; Thu, 29 Sep 2016 23:10:29 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201609292110.u8TLAHgM037995@fire.js.berklix.net> To: Kurt Jaeger cc: Miroslav Lachman <000.fbsd@quip.cz>, Mathieu Arnold , Christian Weisgerber , freebsd-ports@FreeBSD.org Subject: Re: Google Code as an upstream is gone From: "Julian H. Stacey" Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany User-agent: EXMH on FreeBSD http://berklix.eu/free/ X-From: http://www.berklix.eu/~jhs/ In-reply-to: Your message "Thu, 29 Sep 2016 21:10:41 +0200." <20160929191041.GC85563@home.opsec.eu> Date: Thu, 29 Sep 2016 23:10:17 +0200 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2016 21:11:08 -0000 Hi, Reference: > From: Kurt Jaeger > Date: Thu, 29 Sep 2016 21:10:41 +0200 Kurt Jaeger wrote: > Hi! > > > Christian Weisgerber wrote on 09/29/2016 18:57: > > > Mathieu Arnold: > > > > > >> If the software has not been moved to some other place, (it takes about > > >> 30 seconds to click the automatic migration to github thing, and it is > > >> usually done within the hour,) since march 2015, it is most likely > > >> abandoned and should not be kept in the ports tree. > > > > > > That's a bold new policy. > > > > > > In the past, if the upstream was gone and the maintainer judged the > > > software still useful (at their discretion, not based on a cut-off > > > date), they would even fall back to providing the distfile at > > > people.freebsd.org. > > > > I don't think it is good to remove ports just because source was not > > updated for some time. There are ports useful even 10 years after last > > update. Namely pnm2ppa is really old piece of code. It was removed from > > ports tree because there was not maintainer. So I must become a > > maintainer and now the port is alive again. > > I think there should not be policy to remove ports if they have > > maintainer or some user using them if only thing which should be done is > > to change SRC url. > > I agree, old code does not mean it's useless code. Me too. I use loads of old ports, aka stable mature code, not everything needs to be hacked to qualify not to be chopped, some stuff just works :-) > We probably need a way to find out how often a pkg is downloaded > from a repo to understand which ports/pkg are really used in our > user base. This helps to decide if a port is really no longer in use. Insufficient test. I never download packages. I always compile. pkg info | wc -l 1216 I keep old distfiles. Occasionaly i've fed lost distfiles back to the net. PS I guess some of us might not mind enabling a switch on some not all of our boxes, if some auto collector robot @freebsd collected stats on ports, driven by some make post-install or post make package Mk/ macro But it should be off by default: privacy issues. Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes