1 |
Duncan wrote: |
2 |
|
3 |
> Thomas Sachau <tommy@g.o> posted 48E8B217.8020505@g.o, |
4 |
> excerpted below, on Sun, 05 Oct 2008 14:24:55 +0200: |
5 |
> |
6 |
>> I just had a user in bugzilla who thought, the developer profile would |
7 |
>> be for software developers, not just for gentoo developers. Probably he |
8 |
>> is not the only one. |
9 |
>> |
10 |
>> What about either adding some big warning on portage output or renaming |
11 |
>> this profile to e.g. "gentoodeveloper"? |
12 |
>> |
13 |
> |
14 |
> There's a thread in the archive discussing this. The conclusion then |
15 |
> seemed to be that the traditional profile.bashrc test for |
16 |
> I_KNOW_WHAT_I_AM_DOING=yes, with a suitable warning if it wasn't set, |
17 |
> should be enough. |
18 |
> |
19 |
> The problem with that is that the profile itself sets that var in |
20 |
> profiles/targets/developer/make.defaults, so anyone using the profile has |
21 |
> it set automatically, rather defeating the purpose of the test in the |
22 |
> first place. |
23 |
> |
24 |
> The solution would be to remove that bit from profiles/targets/developer |
25 |
> (and other places it may be set in the profiles, forcing those using the |
26 |
> developer profiles to actually set it themselves. If they don't, they |
27 |
> get the warning. |
28 |
|
29 |
That seems like a clean (and simple) solution. |
30 |
|
31 |
> If they see the warning and set it anyway, well, one |
32 |
> would hope they /do/ know what they are doing, and if they don't, as the |
33 |
> saying goes "If it breaks, you (they) get to keep the pieces!" |
34 |
> |
35 |
> I'd suggest a somewhat less generic var as well. Perhaps |
36 |
> I_AM_A_GENTOO_TESTER_AND_I_KNOW_WHAT_I_AM_DOING, or maybe |
37 |
> I_KNOW_THIS_MAY_BREAK_BUT_I_AM_TESTING_AND_KNOW_WHAT_I_AM_DOING. |
38 |
> |
39 |
Wooh, calm down there ;) Longer synonyms with no additional semantic data |
40 |
don't help anyone ime; it's already long enough (and, speaking as an |
41 |
end-user, typing it in does make you stop and think about what you're |
42 |
doing, after you stop laughing, so it does serve its purpose.) |
43 |
|
44 |
> Or make the profile.bashrc test for both the var and a more specific |
45 |
> value, perhaps like this: |
46 |
> |
47 |
> I_KNOW_WHAT_I_AM_DOING="and I know it can break but I am testing" |
48 |
> |
49 |
Hehe. I think just doing what you mentioned above, ie not setting it in the |
50 |
defaults, but allowing the user to do so at installation (or whenever) |
51 |
would solve it. The loud warning notice does put casual users off, and it |
52 |
should be enabled by default for arguably any unsupported profile. |
53 |
|
54 |
Devs will no doubt be quick to set up their own machines as and how they |
55 |
want; expecting a single additional config var in amongst the make.conf |
56 |
template isn't such a big deal, and keeps the support burden down. |