1 |
Micha³ Górny: |
2 |
> |
3 |
> That said, cross-distribution compatibility is important. |
4 |
|
5 |
To be honest, this is a minor case and you shouldn't expect the council |
6 |
to do anything about it. |
7 |
|
8 |
Last time it really made a difference was about the pkgconfig discussion |
9 |
and neither QA nor the council cared enough to enforce consistent rules |
10 |
about it. |
11 |
|
12 |
No one cares about cross-distro compatibility. |
13 |
|
14 |
The more important argument is simplicity imo and maintenance burden. We |
15 |
are not just talking about games supposed to install into |
16 |
/usr/games/bin, but literally in any location, since those games |
17 |
variables are modifiable and advertised as such (so this wasn't really |
18 |
about FHS compliance in the first place). Please look at the downstream |
19 |
patches, sed hacks, symlink workarounds, wrapper scripts and eclasses |
20 |
(even gnome-games.eclass) that were introduced because of this. |
21 |
|
22 |
Sure, it's doable, but still a lot of work to support a corner case. |
23 |
|
24 |
In paludis, if you want to modify permissions for all games globally, |
25 |
you could easily do so via an ebuild phase hook, e.g. |
26 |
|
27 |
# cat /etc/paludis/hooks/ebuild_install_post/games_perms.bash |
28 |
if [[ ${CATEGORY} =~ "games" ]] ; then |
29 |
find /var/tmp/paludis/${CATEGORY}-${PF}/image/usr/bin -type f ... |
30 |
fi |
31 |
|
32 |
I'm not sure why this case has to be supported via an eclass. |