| 1 |
Ferris McCormick wrote: |
| 2 |
|
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA1 |
| 5 |
> |
| 6 |
> This is random musing based based on perhaps my own problems. |
| 7 |
> I need a local color.file to see well what I have going on, and |
| 8 |
> current xorg ignores that. Thus, at every build, there is in |
| 9 |
> oscolor.c a "constant" I must change from 1 to 0. |
| 10 |
> |
| 11 |
I don't understand why this is an issue for "every build"; surely a patched |
| 12 |
ebuild in local overlay is trivial? It's only a quick sed -i line added. |
| 13 |
|
| 14 |
> This is frustrating, especially since the fix is completely trivial |
| 15 |
> on a USE or configure flag. As best as I can tell, xorg people have |
| 16 |
> ignored my request, although it it is real. |
| 17 |
> |
| 18 |
> I am asking if anyone cares if one can give a local rgb file or not, |
| 19 |
> or if I am stuck with "fixing" every update so that it will take mine |
| 20 |
> so that I can see it. Perhaps no one cares but me. Well, so be it, |
| 21 |
> but it slows down xorg-server testing (or upgrading) for me because I |
| 22 |
> have to keep changing that file by hand. I'm really tired of |
| 23 |
> fixing this trivial thing by hand. |
| 24 |
> |
| 25 |
Fair enough for upgrades, it might be worth adding to the ebuild; I |
| 26 |
certainly agree user control of rgb is worth having. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@l.g.o mailing list |
Archives