1 |
On Fri, Jan 23, 2015 at 7:12 PM, <covici@××××××××××.com> wrote: |
2 |
>> On Fri, Jan 23, 2015 at 5:45 PM, shawn wilson <ag4ve.us@×××××.com> wrote: |
3 |
>> > Is there a way to have default config lines that emerge updates won't touch? |
4 |
>> > |
5 |
>> |
6 |
>> I'd be interested in hearing about alternatives, but I switched to |
7 |
>> cfg-update from dispatch-conf and such because it does automatic 3-way |
8 |
>> merging. It is pretty good about detecting stuff that you customized |
9 |
>> and auto-merging those lines as long as the upstream file doesn't |
10 |
>> change. If it does, then you get a 3-way merge in meld or another |
11 |
>> tool to do the merge. 95% of the time it just automerges all config |
12 |
>> file updates without any interaction. |
13 |
>> |
14 |
>> I inherited maintaining this upstream, so feel free to submit |
15 |
>> improvements. It is a fairly mature tool but we've had some great |
16 |
>> contributions to keep it up-to-date with portage/paludis apis. |
17 |
> |
18 |
> I was using that, but it didn't do any automatic 3-way merge for me, I |
19 |
> do everything from a text console. I am now using etc-update which is |
20 |
> not too bad. |
21 |
|
22 |
I'd have to take another look, but I don't think the automatic merge |
23 |
works unless you're using a 3-way diff tool, and I think those are all |
24 |
X11. That doesn't make sense to me - the automatic part at least |
25 |
should be attempted with only a 2-way tool. |
26 |
|
27 |
I need to see if there is anything I can do about that. Also, if you |
28 |
haven't used it in the last year or two try it again. When I took it |
29 |
over we had a flurry of patches which fixed a bunch of little things |
30 |
with it, but it has been quiet for a while. |
31 |
|
32 |
-- |
33 |
Rich |