Date: Thu, 29 Sep 2016 23:10:17 +0200 From: "Julian H. Stacey" <jhs@berklix.com> To: Kurt Jaeger <lists@opsec.eu> Cc: Miroslav Lachman <000.fbsd@quip.cz>, Mathieu Arnold <mat@FreeBSD.org>, Christian Weisgerber <naddy@mips.inka.de>, freebsd-ports@FreeBSD.org Subject: Re: Google Code as an upstream is gone Message-ID: <201609292110.u8TLAHgM037995@fire.js.berklix.net> In-Reply-To: Your message "Thu, 29 Sep 2016 21:10:41 %2B0200." <20160929191041.GC85563@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Reference:
> From: Kurt Jaeger <lists@opsec.eu>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201609292110.u8TLAHgM037995>