On Thu, Mar 12, 2015 at 7:08 PM, Mick <michaelkintz...@gmail.com> wrote: > On Thursday 12 Mar 2015 22:46:14 Mike Gilbert wrote: >> On Wed, Mar 11, 2015 at 7:38 AM, Rich Freeman <ri...@gentoo.org> wrote: >> > On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick <n...@digimed.co.uk> wrote: >> >> On Wed, 11 Mar 2015 06:20:25 +0000, Mick wrote: >> >>> > Google only keeps the latest versions so that ebuild is usually only >> >>> > good for a short while after it gets marked stable. >> >>> > Just keyword the unstable package. >> >>> >> >>> So users of the stable package have to be really fast, or lucky? >> >> >> >> Gentoo should keep a copy in its mirrors for as long as a current ebuild >> >> needs it (unless the package is fetch-restricted). >> > >> > Chrome is mirror-restricted, because of: >> > 9.2 Subject to section 1.2, you may not (and you may not permit anyone >> > else to) copy, modify, create a derivative work of, reverse engineer, >> > decompile or otherwise attempt to extract the source code of the >> > Software or any part thereof, unless this is expressly permitted or >> > required by law, or unless you have been specifically told that you >> > may do so by Google, in writing. >> > >> > chrome-binary-plugins is not free software, or open source. There is >> > little Gentoo can do when they keep changing the URL/hash without >> > warning. >> > >> > You can file a bug to get the ebuild updated though. >> >> As the person doing the bumps, I would actually prefer that people >> ping me in IRC before creating a bug report. It's annoying to have to >> close a bug report for an issue that occurs quite frequently. > > Don't mind doing this if it will help - what's your nick?
floppym -- same as my email address.
