| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
(Note that bzr does not support etckeeper's pre-commit hook.)
|
|
* Pass other patameters on from etckeeper to the .d scripts.
* Stop using run-parts for various reasons.
* Split out a commit.d that contains committing code that's used by
both the pre-install.d and post-install.d scripts.
* Split out an unclean.d that tests if the WC contains uncommitted
changes.
* Add preinst code to remove old post-install.d scripts.
|
|
Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
|
|
Changed the templates file to not hardcode 'git', and manually unfuzzied
all translations except for Vietnamese, which stumped me. A few
translations _may_ read incorrectly when VCS=hg, most should be ok.
Updated git-specific documentation, but left the tutorial git-specific.
Rename more conffiles. Joy oh, joy.
Update dependencies.
Add some more documentation about etckeeper.conf.
|
|
from the release notes of the upcoming 1.5.4 release:
"The next feature release of git (this change is scheduled for v1.6.0) will by
default install dashed form of commands (e.g. "git-commit") outside of users'
normal $PATH"
|
|
in etckeeper.conf.
* Only install apt hooks if apt is used.
* Only add backup conffile exclusion to gitignore if dpkg is used.
* Rename pre/post-apt.d to pre/post-install.d to allow the same directories
to be used for other package managers.
* Use the name of the highlevel package manager in commit messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Default to cding to /etc, but allow the user to specify another directory
to operate on.
|
|
|
|
|
|
|
|
While working on this, I had to consider security policies -- is it ok if
etckeeper init can run code from the /etc repository? I've decided this
should be ok, and documented that it should only be run on trusted repos.
Note that metastore could also be exploited by untrusted repos, and of
course, note that you're checking out your *** /etc *** so it damn well
better be trusted!
With that determined, I decided to use a simple shell script to hold the
empty directory info and allow them to be easily created. Expanding this for
other files git can't represent is a possibility..
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
work around various bugs and issues to avoid each commit making a change that
would be seen by the next commit..
|
|
other development too..
|
|
|
|
|
|
|
