1 |
On Wed, 22 May 2013 03:06:05 +0000 (UTC) |
2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
3 |
|
4 |
> And a knife or hammer can be used to murder or commit suicide as |
5 |
> well; that doesn't mean they're bad tools, it means the user is |
6 |
> misusing them. |
7 |
|
8 |
The amount of users misusing a knife or hammer is much lower than the |
9 |
amount of users misusing INSTALL_MASK. And even if you want to use it |
10 |
as an example, murdering is only bad when you consider it to be bad. |
11 |
|
12 |
Anyhow, the knife and hammer aren't the best tools around to do it as |
13 |
your target will have a high chance of surviving. Unless you target |
14 |
people that don't defend themselves, all you make is a few scratches. |
15 |
|
16 |
> There's more advanced knives and hammers too, but you don't have to |
17 |
> procure the most expensive one to do the job. |
18 |
|
19 |
You do, because better tools cost more effort. |
20 |
|
21 |
> In some cases, even a heavy screwdriver can be used as a hammer, if |
22 |
> that's what you have in your hand and the hammer's down the ladder in |
23 |
> the toolbox. |
24 |
|
25 |
It's this kind of lazyness that ends up breaking things. |
26 |
|
27 |
> > In other Package managers, I assume this madness isn't supported. |
28 |
> |
29 |
> That might be part of why I don't use other PMs... |
30 |
|
31 |
But other users do, because Portage isn't perfect. |
32 |
|
33 |
> > In its current state, it certainly has its use cases; though it is |
34 |
> > often misused by unaware users that don't know what removal of |
35 |
> > certain files has as a consequence, that means it can do more bad |
36 |
> > than good... |
37 |
> > |
38 |
> > [1]: http://forums.gentoo.org/viewtopic-t-670094.html |
39 |
> > First INSTALL_MASK I came across searching for it online, |
40 |
> > particularly masking *.h, *.pc and Makefile* are very bad |
41 |
> > ideas. |
42 |
> |
43 |
> Did you read the use case? He is (was, that was 2008) doing the |
44 |
> builds for his 2GB drive netbook on different build system, then |
45 |
> doing binpkg installs on the netbook. In that case, INSTALL_MASKING |
46 |
> those filetypes for installation to the netbook, where he has no |
47 |
> intention of doing any building anyway, makes quite a lot of sense. |
48 |
|
49 |
A good lesson is that people don't actually read all that stuff, those |
50 |
that are looking for values for INSTALL_MASK will often just try it for |
51 |
themselves only to see these dangerous values fail and start bothering |
52 |
them. Or they may not know it's because of their INSTALL_MASK that they |
53 |
need to reinstall their system some time later. |
54 |
|
55 |
Historically, ricing other settings like the CFLAGS in make.conf is a |
56 |
quite good example of why this file is a red herring; it took quite |
57 |
some time for the concept of SAFE CFLAGS to get some attention. That's |
58 |
why SAFE INSTALL MASKS is amongst one of the suggestions I made in the |
59 |
earlier reply; people on an embedded profile could mask these files, |
60 |
other people cannot unless they _explicitly_ unmask the ability to mask. |
61 |
|
62 |
> In fact, I have a netbook (tho it has a much larger 100+ gig drive) |
63 |
> and could use the idea myself (altho currently I don't run a PM at |
64 |
> all on the netbook, instead rsyncing from the build image on the main |
65 |
> machine, so I'd have to modify his use case... or mine... somewhat). |
66 |
|
67 |
Not running a PM makes this paragraph irrelevant to this discussion. |
68 |
|
69 |
> As for people misusing the available tools, gentoo has always taken |
70 |
> the position that we make the tools available and document how to use |
71 |
> them, but we aren't a babysitting or handholding distro, and if |
72 |
> handholding is what people want/need, they better look elsewhere as |
73 |
> gentoo's simply not in that market, and doesn't pretend to be. |
74 |
|
75 |
We do babysitting / handholding where we can, the _right_ amount of it. |
76 |
|
77 |
Not bringing out news or supporting people with the udev upgrade, that |
78 |
would've cost us people; not working on options that make systemd work, |
79 |
that would've cost us people. Not pointing to solutions for the recent |
80 |
automake errors / genkernel blocker, that would've cost us people. |
81 |
|
82 |
Let's not sacrifice part of our user base by taking a wrong decision; |
83 |
developing a distro goes much further than "let's just use this hack", |
84 |
until multiple people agree a hack to be the best short term solution. |
85 |
|
86 |
Go consistently make the worst tools available, we'll talk again then. |
87 |
|
88 |
-- |
89 |
With kind regards, |
90 |
|
91 |
Tom Wijsman (TomWij) |
92 |
Gentoo Developer |
93 |
|
94 |
E-mail address : TomWij@g.o |
95 |
GPG Public Key : 6D34E57D |
96 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |