Date: Thu, 22 Sep 2016 07:45:53 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: Tijl Coosemans <tijl@FreeBSD.org>, John Marino <freebsd.contact@marino.st>, marino@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r422505 - head/archivers/snappy-java Message-ID: <20160922074553.GA93832@FreeBSD.org> In-Reply-To: <0ebb95f3-0bf5-5c34-c59f-8eb344f92fd7@FreeBSD.org> References: <3bbaf8af-e9d0-9fce-b103-2055bdce8e18@marino.st> <1db2352b-f6b6-ba58-d18d-7d1eac5c4c0f@FreeBSD.org> <202c3516-4c9e-971f-eddc-e3eb904f1ff7@marino.st> <92a0385e-13ac-0a43-4761-103ffa2e9961@FreeBSD.org> <9f4ce30a-70a4-f668-50e0-a35be78b5032@marino.st> <1b891572-9be2-f658-2942-42f5f6168c3d@FreeBSD.org> <3a8164b8-e15d-b955-05fc-3d817d1168d7@marino.st> <20160921211117.54166e17@kalimero.tijl.coosemans.org> <20160921204950.GA83030@FreeBSD.org> <0ebb95f3-0bf5-5c34-c59f-8eb344f92fd7@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 22, 2016 at 08:52:03AM +0200, Mathieu Arnold wrote: > Le 21/09/2016 ?? 22:49, Alexey Dokuchaev a ??crit : > > I was actually wondering why use any distcache instead of Google's Cloud > > URL instead? I did not find them mention that there is an expiration date > > for Google Code project archives, so it's probably OK to assume we have a > > nice read-only storage of those distfiles for the time being, no? > > I'm going to paste the text I wrote last time someone asked that question: I didn't miss this piece of text the first time you posted it, but now I'm talking about something else. ;-) > Before marking all the ports BROKEN, I started by changing the > MASTER_SITE_GOOGLE_CODE entry to make things fetchable again. > The problem with that approach is that it is just hiding the fact that > the software have not been updated for more than a year and will never > be again. The goal of marking all those ports broken is that people will > go and look for where the software went after google code, so that it > gets updated when new releases go out. I understand why you marked them BROKEN rather than trying to fix the MASTER_SITE_GOOGLE_CODE. I was puzzled, however, that when John started to fix those ports, after failing to quickly find working new upstream or distfile he falled back to those GNU/Linux distros' caches instead of pointing to archived distfile in Google's own storage. As I understood, Google had closed their Code project, but distfiles won't go ahywhere (in a near future at least). If I missed their official "this stuff will be completely gone in two years" statement then I'm sorry and don't listen to me. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160922074553.GA93832>