Ok, marking Won't Fix due to the chroot issue and the current way of
doing this is sufficient.
** Changed in: libertine/devel
Status: Triaged => Won't Fix
** No longer affects: libertine/trunk
** Changed in: libertine
Status: Triaged => Won't Fix
** No longer affects: libertine/de
After discussion, I'm not sure if this is possible for chroot based
containers since there really is no concept of "starting" or "opening" a
chroot.
That said, we could possible have some sort of libertine-chroot-manager
that could set this up, but any benefits may not outweigh the work
required a
