Tobias Gruetzmacher wrote: > It would be great if one could force etckeeper to commit the "changes" > after each apt run, even if /etc wasn't changed. As things are now, you > get nice commit messages for each update, install, uninstall, but only > if any of the involved packages changes /etc. Forcing commits would > preserve information over every install/uninstall/update in etckeeper's > history.
etckeeper's mention of package changes is not meant to be a
general-purpose log of such changes. dpkg already generates such a log
in /var/log/dpkg.log*.
etckeeper only mentions package changes because it's a cheap way to get
a general idea of what kind of upgrade caused changes to files in /etc.
If there were better ways to record that information (such as only
recording info about the packages that actually owned the configuration
files that were changed), then etckeeper would use them.
Thus, what you're asking for is both a duplicate feature, and a side
effect of what is currently a suboptimal implementation, which we
certianly don't want to turn into a feature we have to keep long-term, if
better means[1] become available.
--
see shy jo
[1] Such as an eqivilant to rpm's ghost files, which allows a file to
be recorded as part of a package even though it's not shipped as
part of it.
signature.asc
Description: Digital signature
