This is an oversight on my part when I implemented the "global variables" feature. In short, chroot_xxxxx.lst files can have the :file section which allows other xxxxx.lst files to be processed. Well, chroot_setup.sh (line 190) doesn't pass global variables on to the chroot_setup function call. So if the embedded xxxxx.lst file has global variables (i.e. myuser, mydir) then they won't be replaced.
There are a couple ways to address this, and one I am working through changes the approach from being recursive to doing a separate call to chroot_setup.sh so the xxxxx.lst file is processed in the exact same way as the parent who called it.
This issue is to document that we know this issue exists and are working on it. I haven't encountered anyone else with this issue other than myself.
Original report by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).
This is an oversight on my part when I implemented the "global variables" feature. In short,
chroot_xxxxx.lstfiles can have the:filesection which allows otherxxxxx.lstfiles to be processed. Well,chroot_setup.sh(line 190) doesn't pass global variables on to thechroot_setupfunction call. So if the embeddedxxxxx.lstfile has global variables (i.e.myuser,mydir) then they won't be replaced.There are a couple ways to address this, and one I am working through changes the approach from being recursive to doing a separate call to
chroot_setup.shso thexxxxx.lstfile is processed in the exact same way as the parent who called it.This issue is to document that we know this issue exists and are working on it. I haven't encountered anyone else with this issue other than myself.