| Summary: | Need a proper way to install Toaster dependencies | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | devtools / tool chain | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alexandru.damian, meta.mr.watcher, meta.watcher, srifenbark |
| Version: | 1.7 | ||
| Target Milestone: | 1.8 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2014-07-18 14:19:37 UTC
Can you enumrate the complete list of "some other dependencies" beyond Django and South? The Toaster dependencies are listed here: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/toaster-requirements.txt Proper way to install dependencies is: $ virtualenv venv $ source venv/bin/activate $ pip install -r poky/bitbake/toaster-requirements.txt I've tested bitbake and it works fine in an virtualenv, so toaster can be used in managed mode (1.7/1.8 mode) to also run builds. Please reopen with Documentation Change: Yes if we need to change the manual to document this. Reopened because I've seen the need for the recipe. Right, we do need to provide the appropriate dependencies as part of buildtools. We also definitely do need to document the proper procedure in the Toaster manual (when such a thing exists). CCing Scott since we just talked about documenting the Toaster installation procedure. Perhaps contrary to the above, the documented install method will continue to be to use virtualenv + pip, and we are not going to extend buildtools / the build appliance out of the box. For those that prefer an alternative, I have sent recipes to meta-python to build an appropriate version of python-django + python-django-south that can be used to build fixed versions. |