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