Bug 11691 - Divide python-pymongo into python-pymongo and python-bson
Summary: Divide python-pymongo into python-pymongo and python-bson
Status: RESOLVED INVALID
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided enhancement
Target Milestone: ---
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-06-20 10:57 UTC by Johannes Schrimpf
Modified: 2017-06-22 15:11 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Schrimpf 2017-06-20 10:57:17 UTC
python-bson is part of pymongo. However, in many cases it is not necessary to include the whole pymongo packet to meet the dependencies. In popular distributions, the package is divided in two parts where python-pymongo also depends on python-bson but python-bson can be installed separately.

In my specific case, I have a ROS package that depends on python-bson. There is a python-bson in meta-ros but it would be beneficial if a python-bson from meta-python could be used instead of python-bson being maintained in meta-ros. This can prevent version conflicts and make meta-python more general.
Comment 1 Paul Eggleton 2017-06-22 15:05:54 UTC
So this sounds like a reasonable change, however we don't currently track issues in meta-python in this bug tracker, so I'm afraid I'm going to resolve this as invalid.

However, I've added the two meta-python maintainers on CC. If that doesn't elicit a response / action then I'd suggest sending an email to the openembedded-devel mailing list CCing them which is currently the place to report issues with meta-python and other layers in meta-openembedded repo.
Comment 2 Derek Straka 2017-06-22 15:11:08 UTC
I don't see a problem with this.  I can probably knock it out this weekend or next depending on when I do my next round of package updates in master.