1 |
Hi! |
2 |
|
3 |
On Fri, 31 Aug 2007, Mike Frysinger wrote: |
4 |
> On Friday 31 August 2007, Marius Mauch wrote: |
5 |
>> Petteri Räty <betelgeuse@g.o> wrote: |
6 |
>>> Matthias Schwarzott kirjoitti: |
7 |
>>>> On Freitag, 31. August 2007, Matthias Schwarzott wrote: |
8 |
>>>>> What do you think about adding /etc/udev/rules.d/ to |
9 |
>>>>> CONFIG_PROTECT_MASK. This will no longer bother the user with |
10 |
>>>>> updating these files. Thus it will reduce the number of bugs |
11 |
>>>>> triggered by forgotten config-file updates. |
12 |
>>>>> |
13 |
>>>>> If user needs home-brewn rules he is requested to add own files, |
14 |
>>>>> and not use the already existing ones. |
15 |
>>>> |
16 |
>>>> Only problem I see: What to do with people having custom |
17 |
>>>> modifications inside the default rules-files? |
18 |
>>> |
19 |
>>> Can they add /etc/udev/rules.d back to CONFIG_PROTECT in make.conf? |
20 |
>> |
21 |
>> No, that wouldn't work. However they could add '-/etc/udev/rules.d' to |
22 |
>> CONFIG_PROTECT_MASK or add individual files to CONFIG_PROTECT. |
23 |
> |
24 |
> either solution sucks |
25 |
> |
26 |
> the question is, should people be modifying the default rules ? is there |
27 |
> something in the default rules file that they cant accomplish in a sep rules |
28 |
> file ? if so, then the dir cant be masked ... |
29 |
|
30 |
I find the persisten-net-generator.rules particularly annoying |
31 |
(for various reasons including, but not limited to system images |
32 |
and system cloning). |
33 |
|
34 |
So I have an empty file of that name and happily nuke whatever |
35 |
comes along with udev updates. I could of course unmask that |
36 |
file if it were to be masked in the future. |
37 |
|
38 |
Still, this reeks of layers upon layers of customization to me. |
39 |
I'd prefer a more elegant solution - although know of none. The |
40 |
classic approach would be a USE flag to toggle installation of |
41 |
the shipped udev files - which wouldn't work for me, as I only |
42 |
have gripes about *one* of them. |
43 |
|
44 |
There probably simply isn't a simple, elegant solution that is a) |
45 |
not wrong and b) works for just about everybody. |
46 |
|
47 |
Regards, |
48 |
Tobias |
49 |
|
50 |
|
51 |
-- |
52 |
In the future, everyone will be anonymous for 15 minutes. |
53 |
-- |
54 |
gentoo-dev@g.o mailing list |