Gentoo Archives: gentoo-portage-dev

From: Ed Grimm <paranoid@××××××××××××××××××××××.org>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Conary - dispatch-conf
Date: Fri, 12 Nov 2004 09:18:47
Message-Id: Pine.LNX.4.60.0410310747040.27584@mbeq.rq.iarg
In Reply to: Re: [gentoo-portage-dev] Conary - dispatch-conf by LinuxGuy@Cox.net
1 On Thu, 28 Oct 2004 LinuxGuy@×××.net wrote:
2 > On 21:55 Wed 27 Oct , Ed Grimm wrote:
3 >> On Mon, 25 Oct 2004 LinuxGuy@×××.net wrote:
4 >>
5 >>> Hi there, i've been putting in alot of work on dispatch-conf lately,
6 >>> adding features i personally need, and features that it should have.
7 >>> I have a new version of dispatch-conf posted at bug:
8 >>> http://bugs.gentoo.org/show_bug.cgi?id=68618
9 >>>
10 >>> i believe it will solve one of your major problems with
11 >>> dispatch-conf as i have added a new option called "config file
12 >>> freezing" which allows you to specify config files you never want to
13 >>> be overwritten, like /etc/fstab /etc/password and /etc/group and so
14 >>> on. instead it will take the new files that portage tries to pass
15 >>> out and apply them to rcs (or archive them through whatever meathod
16 >>> you are using). I'm also taking suggestions on features to be added,
17 >>> so if you, or anyone else feels there are other features that should
18 >>> be added email me about it and we'll talk about what/how should be
19 >>> added.
20 >>
21 >> This does sound promising. Note that I cannot fathom any reason why I'd
22 >> want Gentoo's suggested updates archived into RCS for frozen files,
23 >> unless they were not placed on the main branch - I use RCS to track my
24 >> own changes, and I don't appreciate <censored>.
25 >>
26 >> Ed
27 >
28 > A good point i suppose, my reasoning for adding the new files to rcs
29 > was in case there were important changes in the new gentoo files that
30 > you needed, though i suppose those files can be grabbed by
31 > recompiling, however if it's a large app that can be a bit of a
32 > hassle. perhaps the new configs for frozen files should be added to a
33 > different archive? or perhaps to another file? filefoo_frozen or
34 > something? i'd like to hear what others think about the issue.
35 >
36 <snip updates plug>
37 >
38 > another feature i was thinking of adding was a simple command line based
39 > way to add/subtract frozen files, like euse -E and -D. anything think
40 > this is a good or bad idea?
41 >
42 > lastly, Ed, i was a little confused by your last statment:
43 > and I don't appreciate <censored>.
44 > i can't think of a swear that fits here, should i be offended? or was
45 > it just a joke? either way, i missed it. oh well.
46 >
47 > i appreciate any feedback on this so i can continue to improve
48 > dispatch-conf
49
50 Not just one word. I think it would've been more clear had I ended with
51
52 and I don't appreciate <rant censored>
53
54 but I didn't think about the inclusion of that additional word. Note
55 that the censored rant was actually more directed at some various
56 proprietary programs with which I've interacted, but the behavior you
57 were talking about sounded the same.
58
59 However, I've since learned that it only updates the RCS in its own RCS
60 store, leaving the default RCS stores alone. So we're all happy on this
61 point.
62
63
64 That having been said... there's one lesson you should've taken from
65 etc-update: vimdiff support.
66
67 Specifically, there appears to be no documentation regarding the
68 interactive merge option, and it appears to assume a fixed screen
69 resolution which is not similar enough to my screen resolution, editing
70 the new file with $EDITOR requires that I make all of my previous edits
71 by hand, by memory, the first time, and under no circumstances does it
72 allow you to view the differences while one updates.
73
74 I suspect that one could add support for this option by testing for the
75 existance of the pager option, and if it is not defined, invoke the
76 'diff' program without piping its output anywhere. (Note: I have gotten
77 some success using a pager of 'cat'. But vimdiff is not really happy
78 with this option; it complains, and there's added latency, sometimes in
79 unpleasant parts of the update.)
80
81 Note that the behavior of dispatch-conf without one of its current
82 mandatory options is probably not what is intended. I cannot be certain
83 of what was intended, but I'd expect it to completely abort, which is
84 not what it did. I'm not fully certain of what it did, but it was
85 something with RCS in its own tree, which did not touch any of my files
86 so far as I'm able to tell.
87
88 Ed
89
90 --
91 gentoo-portage-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-portage-dev] Conary - dispatch-conf LinuxGuy@×××.net