1 |
On Wed, Mar 11, 2015 at 7:38 AM, Rich Freeman <rich0@g.o> wrote: |
2 |
> On Wed, Mar 11, 2015 at 7:05 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
3 |
>> On Wed, 11 Mar 2015 06:20:25 +0000, Mick wrote: |
4 |
>> |
5 |
>>> > Google only keeps the latest versions so that ebuild is usually only |
6 |
>>> > good for a short while after it gets marked stable. |
7 |
>>> > Just keyword the unstable package. |
8 |
>>> |
9 |
>>> So users of the stable package have to be really fast, or lucky? |
10 |
>> |
11 |
>> Gentoo should keep a copy in its mirrors for as long as a current ebuild |
12 |
>> needs it (unless the package is fetch-restricted). |
13 |
> |
14 |
> Chrome is mirror-restricted, because of: |
15 |
> |
16 |
> 9.2 Subject to section 1.2, you may not (and you may not permit anyone |
17 |
> else to) copy, modify, create a derivative work of, reverse engineer, |
18 |
> decompile or otherwise attempt to extract the source code of the |
19 |
> Software or any part thereof, unless this is expressly permitted or |
20 |
> required by law, or unless you have been specifically told that you may |
21 |
> do so by Google, in writing. |
22 |
> |
23 |
> chrome-binary-plugins is not free software, or open source. There is |
24 |
> little Gentoo can do when they keep changing the URL/hash without |
25 |
> warning. |
26 |
> |
27 |
> You can file a bug to get the ebuild updated though. |
28 |
|
29 |
As the person doing the bumps, I would actually prefer that people |
30 |
ping me in IRC before creating a bug report. It's annoying to have to |
31 |
close a bug report for an issue that occurs quite frequently. |