1 |
Yes, this is a good idea in general. |
2 |
On to the particulars: |
3 |
|
4 |
On Friday 30 May 2003 02:30, Seemant Kulleen wrote: |
5 |
> Now, here's the question. Gentoo policy dictates that we do not touch |
6 |
> files in /etc. During emerge, this is fine, we can provide a file to be |
7 |
> etc-update'd. The concern is during emerge unmerge, when a font path is to |
8 |
> be removed. |
9 |
|
10 |
I am not sure I understand the issue: the fontpaths are akin to variable |
11 |
settings - one line corresponding to installed fontdir. Why can't we do |
12 |
something similar to what we do with /etc/env.d? |
13 |
For example have /usr/share/fonts/paths.d directory (or may be |
14 |
/etc/fontpaths.d may be more appropriate) and have every font pacjage install |
15 |
a file containing the corresponding path.. The utility would scan this dir |
16 |
(called from pkg_postinst or somehow automatically otherwise) and update both |
17 |
official config files. Users should not need to mess with these one-liners, |
18 |
so they will get deleted upon unmerge... |
19 |
|
20 |
On Friday 30 May 2003 06:31, Spider wrote: |
21 |
> What will such a tool do about ordering of paths? There is a sticky |
22 |
> issue here when two paths provide the same fonts, something that is |
23 |
> completely legal. Now, anyone who has customized their X to some extent |
24 |
This is more complicated and totally depends on whether there is certain |
25 |
common way to order them or should this be left totally to user. |
26 |
|
27 |
In the former case it is easy to put numbers at the beginning of fontpath |
28 |
files, how it is done with env-vars anyway.. |
29 |
|
30 |
In the latter case users can just rename these files giving them different |
31 |
number so thay they would get appropriately ordered. The files will be kept |
32 |
intact and only the fonts not specifically ordered will get automatic |
33 |
handling.. |
34 |
In this case users will apparently need to keep track of what they are doing, |
35 |
but this stands true for any site-specific modification. |
36 |
May be there is a better way to address this problem still.. |
37 |
|
38 |
George |
39 |
|
40 |
|
41 |
|
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |