Introduce the notion of a 'sample comment'.

- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.

/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 deletions(-)

# Wrapper to build the tools facilities

# List all tools facilities, and parse their scripts

CT_TOOLS_FACILITY_LIST=

for f in "${CT_LIB_DIR}/scripts/build/tools/"*.sh; do

    _f="$(basename "${f}" .sh)"

    _f="${_f#???-}"

    __f="CT_TOOL_${_f}"

    if [ "${!__f}" = "y" ]; then

        CT_DoLog DEBUG "Enabling tool '${_f}'"

        . "${f}"

        CT_TOOLS_FACILITY_LIST="${CT_TOOLS_FACILITY_LIST} ${_f}"

    else

        CT_DoLog DEBUG "Disabling tool '${_f}'"

    fi

done

# Download the tools facilities

do_tools_get() {

    for f in ${CT_TOOLS_FACILITY_LIST}; do

        do_tools_${f}_get

    done

}

# Extract and patch the tools facilities

do_tools_extract() {

    for f in ${CT_TOOLS_FACILITY_LIST}; do

        do_tools_${f}_extract

    done

}

# Build the tools facilities

do_tools() {

    for f in ${CT_TOOLS_FACILITY_LIST}; do

        do_tools_${f}_build

    done

}