bitmake-user-manual-fetching.xml: Added transportuser parameter for SVN

Fixes [YOCTO #6475]

A new parameter has been added to make sure the user is not
passed as the username for the subversion commands with the
SVN fetcher.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Replaced "populate_staging"

There is no "populate_staging" any longer, should be
"populate_sysroot".

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-intro.xml: Minor edits to start of intro chapter

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-intro.xml: More edits to the intro chapter.

Some applied as is, some not applied, some modified.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-execution.xml: Minor edits to execution chapter.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Edits to some operators

Added wording to clearly state immediate or delayed application
for various operators.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Adding some flag examples.

As long as i've understood everything correctly, this is just
throwing in some physical examples of a couple concepts.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Added second conditional metadata example.

I think having a couple real-life examples here would make a huge
difference.

Comment from Scott: I modified the example description to indicate
that it is from an OpenEmbedded metadata-based recipe (i.e from
YP).  We have been trying very hard to keep the BitBake User
Manual as separate as possible from the YP docs.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Removed fakeroot from list

"fakeroot" is now specified as a function attribute, not as a task
flag.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: Fixed whitespace

I noticed that the examples from some patches were not indenting
by 5 spaces.  I have fixed these to be consistent.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: KERNEL_FEATURES example updated.

I added text to separate this example code from the general
BitBake User Manual's spirit of standing alone and away from
YP or OE stuff.  Also, added another space to move the examples
code so that 5 spaces are used for literal indentation.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake-user-manual-metadata.xml: fixed some example whitespace issues

I added some whitespace to bring the example to use 5 spaces
rather than for so that it follows the manual's convention.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
bitbake: update help message for dump-signatures

The bitbake -S had been updated which always reuires an argument, so
update the help info:
- Add the two args in the help message: none and printdiff

- Use type="choice" so that we can get more friendly error messages,
  for example:
  bitbake: error: option -S: invalid choice: 'printdiffX' (choose from 'none', 'printdiff')

- dump-signatures=DUMP_SIGNATURES -> dump-signatures=SIGNATURE_HANDLER

Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
command/runqueue: Fix shutdown logic

If you hit Ctrl+C at the right point, the system processes the request
but merrily continues building. It turns out finish_runqueue() is called
but this doesn't stop the later generation and execution of the
runqueue.

This patch adjusts some of the conditionals to ensure the build really
does stop.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
fetch2: Add module for ClearCase (ccrc://)

The clearcase fetcher is used to retrieve files from a ClearCase
(http://en.wikipedia.org/wiki/Rational_ClearCase) repository.

Usage in the recipe:

    SRC_URI = "ccrc://cc.example.org/ccrc;vob=/example_vob;module=/example_module"
    SRCREV = "EXAMPLE_CLEARCASE_TAG"
    PV = "${@d.getVar("SRCREV").replace("/", "+")}"

The fetcher uses the rcleartool or cleartool remote client, depending on which one is available.

Supported SRC_URI options are:

- vob
    (required) The name of the clearcase VOB (with prepending "/")

- module
    The module in the selected VOB (with prepending "/")

    The module and vob parameters are combined to create
    the following load rule in the view config spec:
                load <vob><module>

- proto
    http or https

Related variables:

    CCASE_CUSTOM_CONFIG_SPEC
            Write a config spec to this variable in your recipe to use it instead
            of the default config spec generated by this fetcher.
            Please note that the SRCREV loses its functionality if you specify
            this variable. SRCREV is still used to label the archive after a fetch,
            but it doesn't define what's fetched.

User credentials:

    When using cleartool:
            The login of cleartool is handled by the system. No special steps needed.

    When using rcleartool:
            In order to use rcleartool with authenticated users an `rcleartool login` is
            necessary before using the fetcher.

Signed-off-by: Dennis Meier <meier.dennis@siemens.com>
Reviewed-by: Roger Meier <r.meier@siemens.com>
Reviewed-by: Christian Liechti <christian.liechti@siemens.com>
Reviewed-by: Henrique Mendonca <henrique.mendonca@siemens.com>
Reviewed-by: Pascal Bach <pascal.bach@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated the the example 'bitbake -h' output to match the actual
output, which has been recently patched to fix the
'-S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER'
option.

Note also, that I have added a new option that has since appeared
in the output but was not in the manual's example.  That option
added is '--token=XMLRPCTOKEN'.

Reported-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
"per-package" should say "per-recipe"

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
toaster: add fields for sourcedir and builddir paths

We add explicit absolute paths for a directory where
the layer sources will be checked out (sourcedir) and
where the build activities will take place.

Adding minimal checking when starting the application in
order to make sure that BuildEnvironment (BE) settings are
usable. This check is ran by the toaster script at startup.

Modify the localhost bbcontroller to use the BE settings
instead of trying to self-configure on checked out sources.

Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
toaster: improved Project models

A layer may live in a subdirectory of a git repository,
so we add a field to track this setting in the Project layers.

We add the Project schedule_build function, which creates
a build request from the current project configuration.

We also fix an import problem with Projects in views.

Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
toaster: move bldcontrol initial_data fixture to code

We move the initial_data fixture to a code migration,
in order to make sure that we don't overwrite modified data.

The data is inserted only if no data is present, instead
of always overwriting the entry.

The check settings returns 0 if the check was ok.

Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>