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