* Tong Sun wrote in grml's BTS on 20100610 / 00:39:

> > But AFAIK grml-chroot isn't yet reliable enough to be able to deal
> > with several instances of grml-chroot at the same time. So this
> > would be an option as soon as grml-chroot provides a stable
> > mechanism/feature for that.

> Having thinking it over again, I now think the best approach is to create a
> function file in  grml-scripts package, say,

> /usr/share/grml-scripts/functions/grml-chroot

> and move all chroot related common functions from grml-chroot and
> grml-debootstrap in there (even we have two set of duplicated
> functionality), then make grml-debootstrap depends on grml-scripts.

> So the integration can happen gradually. Because the integration involves
> only a single file, it is much easy to manage and track.

> How is that?

I don't see the benefit for now. The chroot stuff isn't rocket
science and adding additional depends just increases risk of
breaking stuff.

If grml-chroot can be used without any possible problems I'm fine
with providing grml-chroot as separate package and using that for
grml-debootstrap, but for now I don't think it's worth all the
effort.

Gebi, ACK from your side?

regards,
-mika-