1 |
On Fri, Feb 28, 2014 at 09:31:08PM -0600, William Hubbs wrote: |
2 |
> On Fri, Feb 28, 2014 at 09:47:05PM -0500, Wyatt Epp wrote: |
3 |
> > But let's be real here: if I install something and |
4 |
> > want to configure its system-wide bits, the first place I go is ALWAYS |
5 |
> > /etc. When I don't find it there, with the rest of the system config |
6 |
> > files, my day gets a little worse and I lose a bit of time trying to |
7 |
> > interrogate a search engine for the answer. And that's annoying. |
8 |
> > That sucks. |
9 |
> |
10 |
> This hasn't changed. |
11 |
> The configuration files these packages are putting in /lib are not |
12 |
> meant to be edited; they are the package provided defaults. If you want |
13 |
> to override one of them, you do that in a file with the same path and |
14 |
> name in /etc, like I mentioned in another message in this thread. |
15 |
|
16 |
The problem, as has been explained many many times, is that the rest |
17 |
of the config is somewhere random on the system. But you knew that, |
18 |
right? You were just telling a half-truth, effectively. |
19 |
|
20 |
I for one prefer a distro to do a bit of work and make my life easier, |
21 |
since it makes life easier for everyone who uses the distro. Why the |
22 |
hell should I care if some bindist can't etc-update? WTF does that |
23 |
have to do with Gentoo? |
24 |
|
25 |
If I wanted a shitty distro that didn't bother to do anything at |
26 |
all, I'd use LFS. At least they don't pretend, then fall over themselves |
27 |
to do a crap load of work rather than admit a mistake; that hey, y'know |
28 |
what? Some of those things from 30 years ago were a damn good idea, |
29 |
and maybe just maybe, they worked some of these issues out back then, |
30 |
so we could stand on their shoulders instead of digging through |
31 |
their garbage. |
32 |
|
33 |
-- |
34 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |