From 9a166b9df68f40bff3575a0634769996a1aa6d05 Mon Sep 17 00:00:00 2001 From: Gregory Haynes Date: Tue, 16 Jun 2015 17:03:17 +0000 Subject: [PATCH] Document only exectuables in phase dirs policy Having data files in the phase subdirs is an easy source of confusion in reviews (especially when the data file is a script) and theres really no reason to be putting data files there at this point. Lets make a convention out of not doing this. Change-Id: I99571a2a49e14e8c709af20f6d13d662ac745eb4 --- doc/source/developer/developing_elements.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/source/developer/developing_elements.rst b/doc/source/developer/developing_elements.rst index 245a34dc1..0d5266cde 100644 --- a/doc/source/developer/developing_elements.rst +++ b/doc/source/developer/developing_elements.rst @@ -33,7 +33,10 @@ Phase Subdirectories Make as many of the following subdirectories as you need, depending on what part of the process you need to customise. The subdirectories are executed in the order given here. Scripts within the subdirectories should be named with a -two-digit numeric prefix, and are executed in numeric order. +two-digit numeric prefix, and are executed in numeric order. Only files which +are marked executable (+x) will be run, so other files can be stored in these +directories if needed. As a convention, we try to only store executable scripts +in the phase subdirectories and store data files elsewhere in the element. * root.d: Create or adapt the initial root filesystem content. This is where alternative distribution support is added, or customisations such as