apt2ostree vs rpm-ostree

apt2ostree sounds similar to rpm-ostree - creating the image out of packages, though it's DEBs, not RPMs. I assume the same limitations as with rpm-ostree apply? %pre/%post script sometimes not working as they should, you can't rely on them running on the real target etc.

We build a custom distro based on CentOS atomic host, and discovered that some things won't work in %pre/%post scripts - e.g. if you want to copy some files around, that won't work; I think 'systemctl enable <service>' works, and I'm not sure about adding users or groups. Obviously, if you want to support multiple platforms, the package scripts won't help, because they will not run on the real target.

The way I see it, rpm-ostree is a very interesting project, but it breaks quite a few expectations that came with creating RPM packages, so it feels rather kludgy in this respect. I don't think people are eager to rewrite their RPMs to handle the rpm-ostree workflow.