[Exherbo-dev] [RFC v2] A new approach to CONFIG_PROTECT

Alex Elsayed eternaleye at gmail.com
Sun Mar 31 06:44:36 UTC 2013

Alex Elsayed wrote:

> After all updates have been addressed (which can be checked for by
> testing whether for every file in 'new' there is a corresponding file
> in 'resolved'), 'eclectic config' iterates over
> /etc/.config-protect/resolved/*/* in order of timestamp from oldest to
> newest. For each directory, it moves the original protected files to the

> '/etc/.config-protect/historic/' subdirectory using the exndbam-name of
> the replacing file; then puts the new file in its place. It may be best to
> implement this as a copy to 'historic/' followed by a rename from
> 'resolved/' so as to avoid leaving a time when no file is present.

Just realized I botched this section (specifically, the part about 

What *should* happen is that the resolved/ goes to /, and new/ goes to 
historic/, so that historic/ can act as the "base" for 3-way merges.

More information about the Exherbo-dev mailing list