1 |
> > I'm getting ready to dive into the apache2 install on my server. |
2 |
> > In preparation for this I needed things I wasn't using before like |
3 |
> > IMAP (see thread on web mail systems), MySQL, and ldap. |
4 |
> > |
5 |
> > Being the good little gentoo boy I updated my USE flags to include |
6 |
> > these and other settings that I plan to use but didn't have in before. |
7 |
> > |
8 |
> > And since my USE flags changed, I'm in the middle of doing the |
9 |
> > "emerge --newuse --emptytree world" (it's actually going quite well; |
10 |
> |
11 |
> hum, that seems like a bit of overkill. wouldn't emerge --newuse world |
12 |
> have sufficed? If you only added imap, mysql, and ldap, there should |
13 |
> only be fewer than 150 packages out of 417 that needs to be |
14 |
> recompiled. |
15 |
|
16 |
Well there were actually quite more use flags than that. To prep for |
17 |
apache I added the jpeg, png, xml & xst, php and a bunch of other |
18 |
related flags. Some of them are probably overkill, but it seemed to be |
19 |
a significant enough change to the USE flags that I thought may touch on |
20 |
more of the installed components than such a short list. |
21 |
|
22 |
The --emptytree as well might be overkill, don't know for sure. I |
23 |
thought it would be the safer option to ensure that dependencies, etc., |
24 |
would be covered. Either way it is too late now as the recompiling is |
25 |
almost finished. |
26 |
|
27 |
> > out of 417 packages, only scotty failed due to some sandbox violations |
28 |
> > that I'm not worried about right now). |
29 |
> > |
30 |
> > But that's got me wondering - am I going to be looking at hundreds |
31 |
> > of /etc updates? |
32 |
> |
33 |
> something like that, yes. |
34 |
> |
35 |
> BUT, if you are like me and do not modify most of the configuration |
36 |
> files, LOTS of those files in /etc will get handled automatically by |
37 |
> etc-update... you only need worry about those files you have changed |
38 |
> from the defaults. |
39 |
|
40 |
I tend to get into many of the configuration files for one reason or |
41 |
another adding or removing options that are specific for my site (and I |
42 |
guess I'm a control freak ;-) |
43 |
|
44 |
So on the majority I would be looking at many updates. |
45 |
|
46 |
> > So if I am looking at hundreds of /etc updates that I don't really |
47 |
> > want to have to wade through, what would be the easiest way to purge |
48 |
> > them all? |
49 |
> |
50 |
> My "find" syntax is a bit rusty, but I think running the following as |
51 |
> root might do it: (you can sub -f for -i if you are real adventurous) |
52 |
> |
53 |
> find /etc -name "._cfg00*" -exec /bin/rm -i {}; |
54 |
|
55 |
That's the route I'm probably going to take. Thanks Willie! |
56 |
|
57 |
-- |
58 |
gentoo-user@g.o mailing list |