Google announced on http://google-opensource.blogspot.de/2015/03/farewell-to-google-code.html to close the "Google Code" repositories. The roadmap on this website is March 12, 2015 - New project creation disabled. August 24, 2015 - The site goes read-only. You can still checkout/view project source, issues, and wikis. January 25, 2016 - The project hosting service is closed. You will be able to download a tarball of project source, issues, and wikis. These tarballs will be available throughout the rest of 2016. Several hundred ebuilds rely on Google Code today. Most projects will move soon to github and other providers. Reproducible: Always
What is the purpose of this bug? To enlist all ebuilds using google code? Isn't it a bit premature?
Hi A.S., thank you for your comment on #544092. It is a tracker like #494678 and helps to keep an overview. It is not premature as some projects have already moved to sf, github and the like. It can not be bad to update the ebuilds early. grep 'google' -R --include="*.ebuild" /usr/portage | grep SRC | wc -l reveals that 800+ packages are affected. In the similar bug https://bugs.gentoo.org/show_bug.cgi?id=494678 it took about one year to fix 50 %.
see also: https://www.reddit.com/r/programming/comments/3i58k5/google_code_is_going_readonly_in_about_a_day_it/cudh8wu
Some statistics: grep 'google' -R --include="*.ebuild" /usr/portage | grep SRC | wc -l 654
uh... $ find /usr/portage/metadata/md5-cache -type f -exec grep -l '^SRC_URI=.*google' {} + | wc -l 693 $ find /usr/portage/metadata/md5-cache -type f -exec grep -l '^SRC_URI=.*googlecode' {} + | wc -l 529
we have now a wiki page to organize and document the work while keeping the noise here to the minimum.
