| 1 |
gucharmap didn't have an uptodate ebuild, so I thought I'd put one |
| 2 |
together, but.. |
| 3 |
|
| 4 |
The configure/Makefile for gucharmap-0.6.1 attempts to rebuild the GTK |
| 5 |
input module cache file during install. Obviously portage catches this, |
| 6 |
so what's the best way to handle this? |
| 7 |
|
| 8 |
It basically executes: |
| 9 |
|
| 10 |
gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules |
| 11 |
|
| 12 |
|
| 13 |
The possibilities I can see are: |
| 14 |
|
| 15 |
a) possibly portage has a function to specify that access to |
| 16 |
/etc/gtk-2.0/gtk.immodules is allowed. |
| 17 |
|
| 18 |
or |
| 19 |
|
| 20 |
b) I provide a patch to the sources to stop this happening, then do it |
| 21 |
myself in the ebuild after install. |
| 22 |
|
| 23 |
|
| 24 |
Any other ideas? What's best? |
| 25 |
|
| 26 |
Cheers, |
| 27 |
MAL |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives