1 |
On 31/03/2015 02:46, Dale wrote: |
2 |
> Neil Bothwick wrote: |
3 |
>> On Mon, 30 Mar 2015 08:42:07 -0500, Dale wrote: |
4 |
>> |
5 |
>>>> I find the separate files much easier to manage as all the settings |
6 |
>>>> for each package are kept separate, and easily removed or changed - |
7 |
>>>> for example when I stop using the package. The alternative would be to |
8 |
>>>> comment every entry in the file so I know why I put it there and |
9 |
>>>> whether I still needed it. |
10 |
>>> What I ran into, I'd update say KDE. It would need some packages added |
11 |
>>> to the keyword file. Some may not be KDE but packages that KDE depends |
12 |
>>> on. Well, should those that are KDE go into the KDE file and the ones |
13 |
>>> that are dependencies but not KDE go into a file of its own or what? |
14 |
>> You put them wherever you want! I put them in kde, because that's what |
15 |
>> they are for. That way I know that those entries were required by KDE |
16 |
>> without having to fill the single file with comments. |
17 |
>> |
18 |
>> |
19 |
> |
20 |
> |
21 |
> Yea. We just batting ideas around. For me tho, it just turned into a |
22 |
> nightmare. If I needed to change something, which file is it in? At |
23 |
> one time I had a dozen or so files and digging through each one of them |
24 |
> wastes time. If I have just one file, I open the file and do a ctrl f |
25 |
> and type in what I am looking for. Of course, some of the script geeks |
26 |
> prolly have a sneaky way of searching and finding out which file it is |
27 |
> in but I'm not one of those, most days for sure. |
28 |
> |
29 |
> Anyway, all the diggin just got old for me. You likely have a easy way |
30 |
> of finding it whereas I don't. ;-) |
31 |
|
32 |
It's called grep |
33 |
|
34 |
-- |
35 |
Alan McKinnon |
36 |
alan.mckinnon@×××××.com |