| 1 |
Neil Bothwick wrote: |
| 2 |
> On Fri, 25 Mar 2011 01:33:38 -0500, Dale wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> Naturally this returned a lot so we have to use common sense before |
| 6 |
>> deleting something. That said, what about these: |
| 7 |
>> |
| 8 |
>> /usr/bin/cc |
| 9 |
>> /usr/bin/c++ |
| 10 |
>> /usr/bin/c89 |
| 11 |
>> /usr/bin/gcc |
| 12 |
>> /usr/bin/gcov |
| 13 |
>> /usr/bin/x86_64-pc-linux-gnu-c++ |
| 14 |
>> |
| 15 |
> I think these are created by gcc-config, so don't belong to any package. |
| 16 |
> If you want to do this regularly, I'd suggest creating a list of |
| 17 |
> exceptions that you can exclude from find. You don't need to search |
| 18 |
> everywhere, /{,usr}/{,s}bin, /{,usr}/lib and /opt should be sufficient. |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
So if they were deleted things would still work? Just curious. This is |
| 23 |
a recent install so I wasn't expecting it to find much, just files I |
| 24 |
created basically. I just thought it odd that it found so many files |
| 25 |
and that qfile/equery didn't know where they came from either. |
| 26 |
|
| 27 |
That gcc one bugs me tho. It's in /usr/bin but doesn't belong to a |
| 28 |
package. Just blows my mind, which ain't much right now. lol I got |
| 29 |
to get better meds. |
| 30 |
|
| 31 |
Dale |
| 32 |
|
| 33 |
:-) :-) |
Archives