| 1 |
On Wed, 2015-07-22 at 07:14 -0400, Rich Freeman wrote: |
| 2 |
> On Wed, Jul 22, 2015 at 6:17 AM, Panagiotis Christopoulos |
| 3 |
> <pchrist@g.o> wrote: |
| 4 |
> > |
| 5 |
> > you can subscribe to gentoo-embedded mailing list and ask there, as your product |
| 6 |
> > is embedded. Also, man make.conf and search for CONFIG_PROTECT. If I understood |
| 7 |
> > you correctly, it may be what you need. |
| 8 |
> > |
| 9 |
> |
| 10 |
> That list is certainly a a good place if it is active, but I get the |
| 11 |
> impression that he wants to package/manage his config files in some |
| 12 |
> way. That is, install package foo, and then automatically get his |
| 13 |
> config files for foo. |
| 14 |
|
| 15 |
Yes, I need to be able to change my own config files too over time. |
| 16 |
|
| 17 |
> |
| 18 |
> Short of going to a true config management system, I'd consider just |
| 19 |
> having a tarball/etc full of config files that you unpack after you've |
| 20 |
> set up your system (or clone it from a git repo or whatever). If you |
| 21 |
> have config files for packages you didn't install it isn't a big deal |
| 22 |
> - they just use up a few inodes, and if you install the packages later |
| 23 |
> the CONFIG_PROTECT settings will prevent them from being overwritten. |
| 24 |
> |
| 25 |
> A portage-based alternative is to stick them all in a package(s) |
| 26 |
> (which will generate collision warnings, and since it would respect |
| 27 |
> config protect it would mean you have to merge in all the changes), or |
| 28 |
> fork all the ebuilds. I just don't think portage is really meant as a |
| 29 |
> full-fleged configuration management tool. |
| 30 |
|
| 31 |
There can not be any manual merges after an SW update here. |
| 32 |
|
| 33 |
I started to look at INSTALL_MASK, what if I set INSTALL_MASK |
| 34 |
to point to all conf files I want to manage myself. |
| 35 |
Then /etc/inittab etc. will not be touched when updating init |
| 36 |
|
| 37 |
Then I add my own ebuild containing my modified conf files but how to |
| 38 |
manage INSTALL_MASK, CONFIG_PROTECT etc.? |
| 39 |
Is it possible from within the ebuild change INSTALL_MASK, CONFIG_PROTECT? |
| 40 |
Then I could just zap INSTALL_MASK before installing my files. |
| 41 |
|
| 42 |
|
| 43 |
> Also, if you're doing lots of these installs you might want to look at |
| 44 |
> a true config management tool like ansible or puppet/chef. That could |
| 45 |
> take care of all the installation as well as the configuration, and |
| 46 |
> could be tied into portage. |
| 47 |
|
| 48 |
sound complicated for what I want to do |
Archives