| 1 |
On Thu, 13 Feb 2014 17:01:47 +0100 |
| 2 |
"Stefan G. Weichinger" <lists@×××××.at> wrote: |
| 3 |
|
| 4 |
> I happily use git for local repositories to track configs in /etc or |
| 5 |
> for example, /root/bin or /usr/local/bin (scripts ..) |
| 6 |
> |
| 7 |
> There is also etckeeper, yes, useful as well. |
| 8 |
> |
| 9 |
> But I would like to have some kind of meta-repo for all the |
| 10 |
> gentoo-servers I am responsible for ... some remote repo to pull from. |
| 11 |
> |
| 12 |
> Most files in /etc might be rather identical so it would make sense to |
| 13 |
> only track the individual changes (saves space and bandwidth) |
| 14 |
> |
| 15 |
> Maybe it would be possible to use git-branches for each server? |
| 16 |
|
| 17 |
Yes. |
| 18 |
|
| 19 |
> Does anyone of you already use something like that? |
| 20 |
|
| 21 |
No idea. |
| 22 |
|
| 23 |
> What would be a proper and clever way to do that? |
| 24 |
|
| 25 |
Just do it. |
| 26 |
|
| 27 |
> How do you guys manage this? |
| 28 |
|
| 29 |
Do as you have described, make the most general thing (a master branch) |
| 30 |
and the most specific things (customer branches); when you have that, |
| 31 |
and you daily (or so) sync the customers with the customer branches you |
| 32 |
can proceed with merging (git merge, not an actual join) the customer |
| 33 |
branches with the master branch. |
| 34 |
|
| 35 |
If you come up with a different branching model, you'll still be able |
| 36 |
to do that; given it is completely on the server, anything between the |
| 37 |
most general and the most specific things is entirely in your control. |
| 38 |
|
| 39 |
-- |
| 40 |
With kind regards, |
| 41 |
|
| 42 |
Tom Wijsman (TomWij) |
| 43 |
Gentoo Developer |
| 44 |
|
| 45 |
E-mail address : TomWij@g.o |
| 46 |
GPG Public Key : 6D34E57D |
| 47 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives