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

[Mathieu Arnold]

Le 21/09/2016 à 22:49, Alexey Dokuchaev a écrit :
> On Wed, Sep 21, 2016 at 09:11:17PM +0200, Tijl Coosemans wrote:
>> ...
>> I would say using Fedora's cache is leeching and not very nice.  On the
>> other hand I wouldn't have marked the ports broken.  Use of our distcache
>> for 14 days should be acceptable.  After that you can mark it broken.
> 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:

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.

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.

-- 
Mathieu Arnold


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20160922/7a8382df/attachment.sig>