[oe] naming tasks

[David Farning]

On Wed, Nov 07, 2007 at 08:45:03PM -0700, Chris Larson wrote:
> "EXPORT_FUNCTIONS do_patch" in patch.bbclass just makes do_patch ->
> patch_do_patch.  That way you can override the do_patch function and
> call back to the patch.bbclass do_patch (patch_do_patch) manually if
> need be, but if you don't, do_patch is still defined.
> EXPORT_FUNCTIONS was just a convenience.

That make sense.  Introducing modularity through namespaces.

Thanks
David Farning

> 
> On Nov 7, 2007 12:58 PM, David Farning <dfarning at gmail.com> wrote:
> > Still working on the manual!
> >
> > I've come across a question on how tasks are named.  What is the
> > purpose of the prefix patch in the def patch_do_patch found in
> > the patch class?  Most task seems to be called do_taskname.
> > I am thinking that it has something to do with
> > scope but I am unsure.
> >
> > addtask refers to do_patch and
> > EXPORT_FUNCTIONS refers to do_patch
> >
> > Thanks
> > David
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel at lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> 
> 
> -- 
> Chris Larson - clarson at kergoth dot com
> Dedicated Engineer - MontaVista - clarson at mvista dot com
> Core Developer/Architect - TSLib, BitBake, OpenEmbedded, OpenZaurus
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel