Death of Google Code

Lawrence Velázquez larryv at macports.org
Fri Mar 13 11:34:38 PDT 2015


On Mar 13, 2015, at 2:03 PM, Ryan Schmidt <ryandesign at macports.org> wrote:

> On Mar 13, 2015, at 12:46 PM, Mark Anderson wrote:
> 
>> Do we have any idea what we need to do/should do to prepare for the
>> eventual shutdown of google code? I know a lot of stuff has been
>> abandoning it, but I feel like we've got quite a few ports out there
>> that will be hit.
> 
> Thanks, I was just going to post about this as I just read the
> announcement myself.

The announcement in question:

http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html

> MacPorts mirrors distfiles, so most ports, including those hosted at
> Google Code, should continue to install fine, even if the original
> download location disappears. It is possible that, for whatever
> reason, we failed to mirror some port's distfiles, so there may be
> exceptions.

Ports that fetch using a VCS will stop working, too.

> We should still try to identify which ports are using a Google Code
> project as their homepage or master_sites location, see if the
> projects have already moved elsewhere, and, if so, update the ports.
> And if not, see if the developer has plans to move. And if not,
> encourage them to do so.

A rough count:

    % find ~/Projects/MacPorts/git-svn/trunk/dports \
    >           -name Portfile -exec grep googlecode {} + |
    pipe>   wc -l
         265
    % find ~/Projects/MacPorts/git-svn/trunk/dports \
    >           -name Portfile -exec grep 'code\.google' {} + |
    pipe>   wc -l
         267
    $

vq


More information about the macports-dev mailing list