On Thu, Nov 27, 2008 at 5:44 AM, Michael Prokop <bts@bts.grml.org> wrote:

> I like the base_tgz approach of grml-debootstrap, if you'd like to implement
> that you've my ACK. :)
>
> Regarding --base_sys: is this still valid with current grml-debootstrap?

The --base_sys is no longer necessary. The newly introduced option
--nodebootstrap, ie "Skip debootstrap, only do configuration to the
target", together with the --target option, means the same thing to
it.

The --base_tgz was use to explain the --base_sys option more easily
for me. After thinking over it, I think we'd better not to add it
because it brings more trouble than the little help:

- should we wipe the --target entirely before expanding the tgz file,
or preserver it.
- if user choose not to wipe, but want to overwrite it with files from
the tgz file, how about those left-overs?
- how about .tar.bzip2 compressed files?
- how about other archive files e.g., dar...

It is better leave the user the freedom to prepare the --target
directory the way they want, then invoke grml-debootstrap with the
--nodebootstrap option.

So I think we can close this now.

> And regarding the "layered module architecture": I noticed that your're playing
> with the module layout using live-initramfs. If you have any information that
> might help us in providing this feature or are interested in working on that
> I'd love to hear from you. :)

So far, I have just been putting the modules that I build for slax on
top of grml. It works perfectly, but they are all my home, text or
script files. I.e., no debian packages involved in the layered modules
yet. I have something in mind how to go about the debian packages.
I've successfully split debian packages info dir in var into a
separated module. The next step would be install grml-full on top of
grml-media, and capture the changes using aufs, but haven't get time
to go further yet. I'll definitely report back if I make any
successful progress on it.

cheers