This is the last do_foo documentation update I wanted to submit for now, so don't worry about more ticket spam. :P

Here's an updated version that also mentions that the do_deploy task needs to be manually added with addtask:

  8.1.7. do_deploy
  
  Writes output files that are to be deployed to ${DEPLOY_DIR_IMAGE}. Runs with
  the current working directory set to ${B}.
  
  Recipes implementing this task should inherit deploy.bbclass and should write
  the output to ${DEPLOYDIR} (not to be confused with ${DEPLOY_DIR}).
  deploy.bbclass sets up do_deploy a shared state (sstate) task that can be
  accelerated through sstate use. The sstate mechanism takes care of copying
  the output from ${DEPLOYDIR} to ${DEPLOY_DIR_IMAGE}.

  Note {
  Do not write the output directly to ${DEPLOY_DIR_IMAGE}, as this will cause the
  sstate mechanism to malfunction.
  }  

  'do_deploy' is not added as a task by default and needs to be added manually.
  This can be accomplished with e.g.

    addtask deploy after do_compile

  if do_deploy should run some time after do_compile. base.bbclass has

    do_build[recrdeptask] += "do_deploy"

  , which makes sure all do_deploy tasks run by default (see the
  [Dependencies](https://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual.html#dependencies)
  section of the BitBake User Manual).

  If do_deploy is re-executed, any previous output is removed (i.e. "cleaned").

Ulf, 

See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#ref-tasks-deploy.  The last part you need to look at closely as I was unsure of some things.  

Also, I don't consider this Bug spam.... these tasks, when originally created, were basically place holders and nobody has gotten around to digging into the brief descriptions much.  So thanks very much for you efforts!

Scott

Thanks. I was thinking of staggering the bugs over a few days at first, but then I got restless. :)


All of the following was supposed to be one sentence:

  This can be accomplished with e.g.

    addtask deploy after do_compile

  if do_deploy should run some time after do_compile.

That's probably unnecessarily confusing though. Here's an attempt to be clearer:

  The do_deploy task is not added as a task by default and needs to be added
  manually. If you want it to run after do_compile, you can add it by doing the
  following:
  
       addtask deploy after do_compile
  
  Adding do_deploy after other tasks works the same way.
  
  Note {
  You do not need to add 'before do_build' to the addtask command (though it is
  harmless), because base.bbclass has the following:
  
       do_build[recrdeptask] += "do_deploy"
  
  See the "Dependencies" section in the BitBake User Manual for more information.
  }
  
  If the do_deploy task re-executes, any previous output is removed (i.e.
  "cleaned"). 


It would be nice if the following could be added to '3.9.4. Recursive Dependencies' in the BitBake User Manual as well, because without it the added Note doesn't make sense:

Replace

  This statement says that the do_packagedata task of all recipes reachable...

with

  This statement says that the do_packagedata task of the current recipe and all recipes reachable...


Thanks,
Ulf

Ulf, 

Here is the change for do_deploy - http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#ref-tasks-deploy.  Thanks for clearing things up for me.

Here is the change in the BB manual - http://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual.html#recursive-dependencies

thanks, 
Scott

Looks good to me!

Thanks,
Ulf

Thanks, 

Resetting everything.