On Tue, Dec 15, 2015 at 12:37 AM J. Randall Owens <jrowens.fedora@xxxxxxxxxxx> wrote:
On 12/14/2015 02:47 PM, Christopher wrote:
> On Mon, Dec 14, 2015 at 11:22 AM Reindl Harald <h.reindl@xxxxxxxxxxxxx
> <mailto:h.reindl@xxxxxxxxxxxxx>> wrote:
>
> i modified my "httpd.conf" based on Apache 2.2 years ago, as Fedora
> swicthed to Apache 2.4 your approach would have compared a customized
> Apache 2.2 version with a Fedora 2.4 version
>
>
> But, that's precisely what I want to do.... I want to know which fields
> in the current configuration could possibly have introduced a breakage I
> see... or which changes I need to make from a clean installation to get
> a user back to the state they wanted.
>
But in order to do the former, you'd best compare the new default to the
old default, to see what had changed in the default. (E.g. distro 2.2 to
distro 2.4) To do the latter, you'd compare the old default (distro 2.2)
to your modified version (altered 2.2), to see what you'd changed
locally. And yet, you seem to be proposing comparing the new default to
the old default (distro 2.4 to altered 2.2), which gets you neither? (Or
both, really, but uselessly mashed together so you don't know which is
which.) Am I missing something?
I'm less interested in what the user intended to change in an older version than the full difference between the current default (presumably working) configs and the current files (which would include any user modifications AND any old defaults carried forward). The current system breakage could be the result of user edits, or a carry-forward of an older config. I don't care which is the case... I just want to see the differences to troubleshoot the problem... I just want to fix the system as it exists today... not question user edit decisions which occurred years ago.
Certainly, a full history, tracking all user edits, and all system updates, would be useful to some. It's just more than what I personally need, and seems a bit outside the scope of the existing installer tools (as previously stated with the suggestion to use etckeeper).
For now, I think I'm going to write a script to parse the output of `rpm -V` and then `dnf download` all the packages corresponding to changed configs, then extract each rpm's %config files, to compare with those on the system. It's messy, but it'll work, and in the absence of rpm storing the full configs or being able to instruct rpm/dnf to reset configs back to the defaults (after backing up), there doesn't seem to be an existing solution that will give me the same result.
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
