1 |
Portage's dispatch-conf does historically only support RCS for |
2 |
configuration file archival. There are currently two unresolved |
3 |
feature requests to extend dispatch-conf support for further |
4 |
configuration file management tools: |
5 |
|
6 |
- bug #260623 git support for dispatch-conf [1] |
7 |
- bug #698316 etckeeper support for dispatch-conf [2] |
8 |
|
9 |
Extending dispatch-conf by a hook directory, which can be used by |
10 |
configuration file management tools to receive notifications about |
11 |
dispatch-conf updating a configuration file, appears to be flexible |
12 |
approach to satisfy those feature requests (or at least lay the |
13 |
groundwork for them). |
14 |
|
15 |
Attached is a patch with a prototypical implementation for |
16 |
conf-update.d hooks. I am curious whether or not you deem this useful |
17 |
enough to get into dispatch-conf. If my suggested approach is |
18 |
considered sensible, then I am happy to continue the work on it. For |
19 |
example, I want to write a unit test for this. But I am not sure if |
20 |
portage's test framework already provides the necessary functionality |
21 |
to create test scenarios for the conf-update.d hooks. Any pointers and |
22 |
further feedback would be much appreciated. |
23 |
|
24 |
- Florian |
25 |
|
26 |
1: https://bugs.gentoo.org/260623 |
27 |
2: https://bugs.gentoo.org/698316 |