svn commit: r422505 - head/archivers/snappy-java

[Alexey Dokuchaev]

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