Re: [atomic-devel] adding post-processing scripts

[Colin Walters <walters verbum org>]

Sorry about the late reply, catching up after some time off:

On Fri, Aug 22, 2014, at 03:32 AM, Karanbir Singh wrote:
> hi,
> 
> whats the process to get post rpm content processing done, aka the %post
> section on a kickstart.

What do you want to do?

The thing is - if you go down this path, you end up with tree content
that isn't
described by RPM.  My take on rpm-ostree was to have a fairly rigorous
constraint that a tree can be described by the RPM database.

There's plenty of configuration management tools out there like
Ansible/Puppet
(in the cloud case, bootstrapped via cloud-init) that I think should be
templating
systems as they always have.

You *could* choose to do configuration management bits in rpm-ostree,
but
it'd seem pretty heavyweight to me.  

One bit of postprocessing that is available right now is the "units"
directive;
this just ultimately creates symlinks for systemd - it's not dependent
on the
target OS.

Postprocessing that involves running code on the target system (e.g.
passwd -d) is more complex.