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