| 1 |
On Wed, Jul 22, 2015 at 6:17 AM, Panagiotis Christopoulos |
| 2 |
<pchrist@g.o> wrote: |
| 3 |
> |
| 4 |
> you can subscribe to gentoo-embedded mailing list and ask there, as your product |
| 5 |
> is embedded. Also, man make.conf and search for CONFIG_PROTECT. If I understood |
| 6 |
> you correctly, it may be what you need. |
| 7 |
> |
| 8 |
|
| 9 |
That list is certainly a a good place if it is active, but I get the |
| 10 |
impression that he wants to package/manage his config files in some |
| 11 |
way. That is, install package foo, and then automatically get his |
| 12 |
config files for foo. |
| 13 |
|
| 14 |
Short of going to a true config management system, I'd consider just |
| 15 |
having a tarball/etc full of config files that you unpack after you've |
| 16 |
set up your system (or clone it from a git repo or whatever). If you |
| 17 |
have config files for packages you didn't install it isn't a big deal |
| 18 |
- they just use up a few inodes, and if you install the packages later |
| 19 |
the CONFIG_PROTECT settings will prevent them from being overwritten. |
| 20 |
|
| 21 |
A portage-based alternative is to stick them all in a package(s) |
| 22 |
(which will generate collision warnings, and since it would respect |
| 23 |
config protect it would mean you have to merge in all the changes), or |
| 24 |
fork all the ebuilds. I just don't think portage is really meant as a |
| 25 |
full-fleged configuration management tool. |
| 26 |
|
| 27 |
Also, if you're doing lots of these installs you might want to look at |
| 28 |
a true config management tool like ansible or puppet/chef. That could |
| 29 |
take care of all the installation as well as the configuration, and |
| 30 |
could be tied into portage. |
| 31 |
|
| 32 |
-- |
| 33 |
Rich |
Archives