Comment 7 for bug 1577514

jdstrand asked me to comment here (I believe I was the "This came up again on IRC today" from the previous comment).

The situation I face is packaging OpenStack with snappy and working with other OpenStack projects for deployment (specifically OpenStack-Ansible). I don't always have control over where it is going to lay down config files. If I could map /etc/foo into ${SNAP_DATA}/etc/foo this would work beautifully.

While that may be a very specific use case, having the ability to map in /etc/foo allows for the seamless transition from traditional packages to snappy. I can't imagine this will do anything but drive up adoption.