On Sat, 5 Nov 2016 08:38:22 +0100 "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote:
> On 05/11/2016 00:54, Jonas Stein wrote: > > Today we have still 524 ebuilds with SRC_URI=*googlecode* in the tree > > [2] and should get these fixed before end of 2016. > > > > [3] https://wiki.gentoo.org/wiki/Shutdown_of_google_code > > The wiki page seems to indicate some sense of urgency. I'm not sure how > much of that is needed. > > Brainstorming mentions just cloning the URLs, but don't existing Gentoo > Mirrors have the same effect? My understanding is fetching will not > break even if original URLs go down. Thou shalt not rely on the mirrors! Though mirrors as a temporary solution are acceptable. As long as you don't turn it into 'wrong SRC_URI is fine, the file is on the mirrors'. > I'm also not fully convinced by the manpower argument. It seems the same > work needs to be done, one way or another. > > For the parts that can be automated and done in batch, this is indeed > more effective than 500 individual bugs. > > However, I'm not sure if finding the new homepage and download URL can > be that easily automated. In fact, users may do some work for us and > help point to the right page. Also, it would be nice not to have the berlios -> sourceforge crap repeated. If software is dead-dead, we should lastrite it or revive it, not point to some dead copy by malware hosting provider. -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgphIkyAzZUIj.pgp
Description: OpenPGP digital signature
