Apparently, though unproven, at 00:02 on Thursday 11 November 2010, Enrico Weigelt did opine thusly:
> * Alan McKinnon <alan.mckin...@gmail.com> wrote: > > Apparently, though unproven, at 23:37 on Wednesday 10 November 2010, > > Enrico > > > > Weigelt did opine thusly: > > > * Remy Blank <remy.bl...@pobox.com> wrote: > > > > Put your /etc under SVN, or Mercurial, or whatever revision control > > > > system du jour. Bonus points if you manage to store file and > > > > directory permissions in there as well. > > > > > > Is there a way to tell portage to conf-protected files under > > > some prefix ? This would allow easy integration into an > > > semi-automated vcs workflow. > > > > CONFIG_PROTECT > > > > in make.conf(5) > > According to the manpage, this only tells which directories should > be config-protect'ed. What I need is that these files should be put > under some prefix (w/ the same hierachy/names) instead of renamed > to ._cfg*. What version of portage are you running? Mine is 2.2.0_alpha4 and the man page says: CONFIG_PROTECT = [space delimited list of files and/or directories] All files and/or directories that are defined here will have "config file protection" enabled for them. See the CONFIGURATION FILES section of emerge(1) for more information. -- alan dot mckinnon at gmail dot com