[lxc-devel] [PATCH 3/3] Let lxc-start read container name from rcfile if not specified on command line

[Andrian Nord]

> But now i'm struggling with the patch :-) - considering the plan to 
> have a 'lxc' binary which invokes subsystems.
> 
> The patch makes it easier to use lxc-start, but when we have a lxc 
> command, the user is not intended to run lxc-start himself anyway.
> So this somewhat renders the patch useless as the lxc binary can of
> course determine the container name and provide it on the command 
> line.

Yeap, yeap. That I was talking about initialy - all utilities should
share same arguments logic, or it would be hard to unite them in single
wrapper (I'm also think, that git-alike wrapper would be nice).

> The lxc command probably would take an even more complex config file
> format, allowing e.g. include, text replacement etc. and would write 
> out a rcfile on the fly suitable for lxc-start and use other parameters
> as needed.

You've got same vision as I am, I suppose. I've done config.include and
variables patches to have exactly such features - to be able to use
common config.

But, if you want to have separate config file syntax and so on -
probably it would be best to 

1) split lxc and liblxc
2) remove any config source from liblxc - it should provide interface
for queuing, changing and writing configuration parameters.
3) implement lxc wrapper as ui for liblxc. And there whould be ability
to implement any other ui (there is such ability, already, but liblxc
contains useless code in such case).