1 |
On Mon, Nov 7, 2011 at 9:58 AM, Samuli Suominen <ssuominen@g.o> wrote: |
2 |
> I don't think that will cut it... It's not the only unhandled compiz bug |
3 |
> in tree[1]. Not sure why it should be given any special status, if it's |
4 |
> not maintained and broken, it should just be punted. |
5 |
> |
6 |
> Also blender should go, since we have had nothing usable in tree for a |
7 |
> while[2]. |
8 |
> |
9 |
> [1] http://tinyurl.com/css37zx |
10 |
> [2] http://tinyurl.com/ckur2jz |
11 |
|
12 |
IMHO, punting a high-profile, widely-used package like blender is an |
13 |
option of last resort. It's not something we can do if gentoo wants to |
14 |
continue calling itself a major distro. As for "nothing usable in |
15 |
tree", most of the bugs are about optional USE-flag controlled |
16 |
features and/or the ancient 2.4x releases. Blender-2.57 with |
17 |
USE=-ffmpeg builds and runs fine. |
18 |
|
19 |
A real issue is that gentoo ships patches to improve blender security |
20 |
defaults that upstream apparently does not care much about (see |
21 |
http://lwn.net/Articles/452273/), and therefore these patches have to |
22 |
be updated on every version bump, which increases maintenance burden |
23 |
and delays getting new versions in portage - new versions that may |
24 |
well contain fixes for the bugs in Samuli's list. Given the lack of |
25 |
manpower for maintaining blender, perhaps replacing the patches with a |
26 |
big ewarn in pkg_postinst might be a less bad longterm solution. |
27 |
|
28 |
In any case, comment 14 of bug #382097 seems to indicate that at least |
29 |
one person will be willing to maintain blender starting in January |
30 |
2012. |
31 |
|
32 |
-Alexandre. |