Exporting the LXCPATH itself to hook scripts seems good. I don't see the value in having multiple LXCPATHs in the hook scripts.
As for allowing ':'-separated paths in LXCPATH, it shouldn't interfere with anything we have now, so if someone wants to work on the patch I'll look at it, but really I don't see advantages to it. And I do see negatives. Think about user jschmoe who has LXCPATH=/home/jschmoe/lxcbase:/var/lib/lxc. Now sudo'd to root he does an lxc-create. It'll end up in /home/jschmoe/lxcbase instead of /var/lib/lxc. I haven't *really* thought through it though, so a well-written patch with a good description would be fine. More useful IMO would be per-user lxc.conf and default.conf files in a standard location. So $HOME/.local/share/lxc/lxc.conf has LXCPATH=$HOME/lxcbase, and $HOME/.local/share/lxc/default.conf has appropriate lxc.idmap entries. A patch like that would also be very welcome. -serge ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ lxc-devel mailing list lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
