On Wed, Jun 9, 2010 at 6:51 AM, Michael Prokop
<bts@bts.grml.org> wrote:
> I believe that the chroot part in grml-debootstrap and grml-chroot share a good
> portion of common ground in preparing chroot, and restoring it. So would it a
> good idea to split out chroot part of grml-debootstrap into grml-chroot, so that
> we have a single code base to maintain/enhance?
Nice idea!
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?