Ian Wienand 9e392f56b0 Don't set tracing in environment files ... Because environment files are sourced into the current environment, they shouldn't be setting global settings like tracing else they affect every preceeding import. This is quite confusing when only half your imports are traced in the logs, because it was either turned on, or off, by a preceeding environment import. There is a corresponding dib-run-parts change in I29f7df1514aeb988222d1094e8269eddb485c2a0 that will greatly increase debugability for environment files by deliberately logging what files are sourced and consistently turning on tracing around their import. This isn't strictly necessary (since dib-run-parts with the prior change will just turn tracing off after import anyway) but it's a decent cleanup for consistency. A bare-minimum dib-lint check is added. Documentation is updated. Change-Id: I10f68be0642835a04af7e5a2bc101502f61e5357		2016-10-20 13:58:00 +11:00
..
dib-lint	Don't set tracing in environment files	2016-10-20 13:58:00 +11:00
disk-image-create	Create (md5|sha256) checksum files for images	2016-10-05 19:34:03 -04:00
diskimage_builder	Add a simple implementation of element dependency	2013-01-23 16:04:20 -08:00
element-info	Use env python	2014-12-08 13:42:16 -08:00
ramdisk-image-create	Build ramdisks in an image chroot.	2013-07-12 11:09:35 +01:00