Re: [gentoo-portage-dev] Managing etc/* in an embbeded system

[Joakim Tjernlund <joakim.tjernlund@transmode.se>]

On Wed, 2015-07-22 at 08:45 -0700, Brian Dolbec wrote:
> On Wed, 22 Jul 2015 09:27:36 +0000
> Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> 
> > We got an embedded gentoo system where we need to manage many conf
> > files under /etc that we have modified and should be under our
> > control when an SW upgrade is performed.
> > 
> > Cloning every ebuild where we have modified its conf file(s)
> > under /etc feels awkward so I am looking for some other way to do
> > this automatically during SW upgrade and I figured this can not be an
> > unique problem for us, so I wonder how other people have solved this
> > problem? Our customers will not use emerge directly and we will
> > provide binary pkgs.
> > 
> > Any ideas welcome :)
> > 
> >  Jocke  
> 
> I see you've been getting good responses to your gentoo-dev copy of
> this email... :)

Yes, plenty!

> 
> We have nothing extra to offer.  As was stated, portage was not
> designed for speciality config management.
> 

Here is your chance then :)
Seems one can do stuff with package.env and friends but these are not in the profile?
Ideally I would like to provide as much as possible via a custom profile and just
have individual stuff(as per machine) in /etc/portage

Even better if one can just add your own conf files inside the profile and these take
precedence over any files in an ebuild.

    Jocke