Bug 11182 - Make it easier to add Python to an image
Summary: Make it easier to add Python to an image
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.4 M1
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-17 15:28 UTC by Joshua Lock
Modified: 2017-05-23 10:53 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

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 Joshua Lock 2017-03-17 15:28:30 UTC 
Currently to get a functional Python in an image a user must add python-core and the correct set of required modules for their Python usage (or all modules with python-modules).

This is a usability trap because a) many modules don't have the correct RDEPENDS and b) most users expect adding 'python' to the image to work, whereas one must actually add 'python-core'

Make it easier to add Python to an image by:
1) having python-core RRECOMMENDS python-modules
2) adding a new package 'python' to the recipe which brings in python-core and python-modules
Comment 1 Ross Burton 2017-04-24 15:52:19 UTC 
(2) done by "python3: add python3 metapackage" on the list.

Not sure if this means we need to do (1) at all.
Comment 2 Alejandro Hernandez 2017-05-12 17:56:13 UTC 
(1) Should be fixed once python smart autopackaging is integrated, this is partly done but I will file an enhancement bug so we can keep track of this.
Comment 3 Ross Burton 2017-05-23 10:53:00 UTC 
(2) is solved by oe-core 54a2549802a911cad2475a6aa379315a834419d8.

I now think that (1) isn't required, as people won't be accidentally including python3-core in images anymore.