On 04/18/2012 03:41 PM, Osier Yang wrote:
On 2012年04月18日 15:41, Guannan Ren wrote:
On 04/18/2012 01:49 PM, Osier Yang wrote:
--- env.cfg => conf/env.cfg | 0 kickstart.cfg => conf/kickstart.cfg | 0 exception.py | 2 +- generator.py | 2 +- parser.py | 4 ++-- repos/domain/install_image.py | 2 +- repos/domain/install_linux_cdrom.py | 2 +- repos/domain/install_linux_check.py | 2 +- repos/domain/install_linux_net.py | 4 ++-- repos/domain/install_windows_cdrom.py | 6 +++--- .../multiple_thread_block_on_domain_create.py | 2 +- 11 files changed, 13 insertions(+), 13 deletions(-) rename env.cfg => conf/env.cfg (100%) rename kickstart.cfg => conf/kickstart.cfg (100%)
the conf file should be in the root directory, just like the Makefile.am or Makefile, we don't need to hide it It's the interface to user.
It's not hidden, doesn't "conf" tells it stores the config files? Let's orgnize things in a good manner, but not throw everything under source root. Makefile is the different story, no comparability.
Osier
The files in the root directory should be import to user. I really think the conf files should be seen directly when users want to edit it. Just like the global_config.ini and shadow_config.ini files in autotest, they are just in the root level. Guannan Ren