Bug 3576 - clean up hob and bitbake interaction via well-defined APIs/abstractions
Summary: clean up hob and bitbake interaction via well-defined APIs/abstractions
Status: VERIFIED NOTABUG
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 1.4
Assignee: Bogdan Marinescu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 3211
  Show dependency tree
 
Reported: 2012-12-12 18:35 UTC by Jessica
Modified: 2013-04-09 13:52 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica 2012-12-12 18:35:36 UTC 

    


    


      



        
          Comment 1
        

        
          Bogdan Marinescu

        

        
        

        
          2013-01-17 14:51:51 UTC
        

      






This bug needs more information. What part of the hob/bitbake interaction needs to be clarified/improved?

    


    


      



        
          Comment 2
        

        
          Bogdan Marinescu

        

        
        

        
          2013-01-22 14:37:49 UTC
        

      






Switching to "NEEDINFO" (see my previous question).

    


    


      



        
          Comment 3
        

        
          Jessica

        

        
        

        
          2013-01-28 22:26:58 UTC
        

      






Bogdan,

THis will be covered in our overall design for bitbake to better support client/server architecture.  We need a well designed (if in place) and documented abstract API layer for client to interact with bitbake server.

    


    


      



        
          Comment 4
        

        
          Bogdan Marinescu

        

        
        

        
          2013-01-31 13:57:32 UTC
        

      






As discussed with Jessica and Richard, the current API is most likely generic enough for what we're trying to achieve. Its documentation should be improved, but that's the subject for another bug, so I'm closing this one.

    


    


      



        
          Comment 5
        

        
          Mihai Lindner

        

        
        

        
          2013-04-09 13:52:51 UTC
        

      






Not a bug.