1 |
On 5/9/17 8:01 AM, Thomas Deutschmann wrote: |
2 |
> On 2017-05-09 10:12, Rich Freeman wrote: |
3 |
>> Why not? If an arch is considered a non-security-supported arch |
4 |
>> then you would just ignore it in a security bug. |
5 |
> |
6 |
> We dropped security coverage already for ia64 and are in the process to |
7 |
> drop it for sparc as well. |
8 |
> |
9 |
> So how do you want to cleanup a package which is the last ebuild of the |
10 |
> package and still marked stabled for ia64/sparc? You cannot. If you are |
11 |
> lucky you would only remove a package without any rdeps. But in most |
12 |
> cases you are breaking the tree. |
13 |
> |
14 |
> |
15 |
>> Otherwise a revbump could break stage3 on those arches. |
16 |
> |
17 |
> Is this really a problem? What could happen: |
18 |
> |
19 |
> Worst case: Existing stage3 for this specific dev/exp architecture will |
20 |
> be very old because any attempt to refresh the stage3 image will fail |
21 |
> with a build error. However, the last working stage3 image won't go away |
22 |
> until it was replaced by a newer working one... |
23 |
> |
24 |
|
25 |
I maintain quite a few ppc stage3's for uclibc and musl. I would |
26 |
appreciate keeping ppc as is. It is still a useful arch for many |
27 |
devices today, eg. some high end Mikrotik routers. |
28 |
|
29 |
|
30 |
-- |
31 |
Anthony G. Basile, Ph.D. |
32 |
Gentoo Linux Developer [Hardened] |
33 |
E-Mail : blueness@g.o |
34 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
35 |
GnuPG ID : F52D4BBA |