<br><br><div class="gmail_quote">On Wed, Jun 9, 2010 at 6:51 AM, Michael Prokop <span dir="ltr"><<a href="mailto:bts@bts.grml.org">bts@bts.grml.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="im">
> I believe that the chroot part in grml-debootstrap and grml-chroot share a good<br>
> portion of common ground in preparing chroot, and restoring it. So would it a<br>
> good idea to split out chroot part of grml-debootstrap into grml-chroot, so that<br>
> we have a single code base to maintain/enhance?<br>
<br>
</div>Nice idea!<br>
<br>
But AFAIK grml-chroot isn't yet reliable enough to be able to deal<br>
with several instances of grml-chroot at the same time. So this<br>
would be an option as soon as grml-chroot provides a stable<br>
mechanism/feature for that.<br></blockquote><div style=""><br>Having thinking it over again, I now think the best approach is to create a function file in grml-scripts package, say,<br><br>/usr/share/grml-scripts/functions/grml-chroot<br>
<br>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. <br><br>So the integration can happen gradually. Because the integration involves only a single file, it is much easy to manage and track. <br>
<br>How is that?<br><br></div></div>