[lxc-devel] More problems with command option conventions...

[Michael H. Warfield]

Hey all!

I've been helping someone by reviewing an article they're writing about
LXC.  An issue just came up that point out a glaring inconsistency in
our use of command option parameters in creating containers from
templates.

In the templates, we're specifying the path to the container directory
as "--path" or "-p".  But, in arguments.c, the same information is
provided by -P (cap) or --lxcpath.  So one convention is used before the
double dash "--" and a different convention after for the same
information.

That's not good, is it???

Should we fix that inconsistency?  Which way?  Should that information
be specified in that manner?  What would be the result of something like
this:

lxc-create --lxcpath /var/lib/lxc -n foo -t fedora -- --path /srv/foobar

Regards,
Mike
-- 
Michael H. Warfield (AI4NB) | (770) 978-7061 |  mhw at WittsEnd.com
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0x674627FF        | possible worlds.  A pessimist is sure of it!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20140201/0ce2fea0/attachment.pgp>