Can the common portions be pulled out into a .inc file that can be included in the python and python3 recipes or was there a specific reason not to do that?
-Derek On Tue, Jul 26, 2016 at 11:03 PM, Chen Qi <[email protected]> wrote: > Signed-off-by: Chen Qi <[email protected]> > --- > meta-python/recipes-devtools/python/python3-pip_8.1.2.bb | 13 > +++++++++++++ > 1 file changed, 13 insertions(+) > create mode 100644 meta-python/recipes-devtools/python/ > python3-pip_8.1.2.bb > > diff --git a/meta-python/recipes-devtools/python/python3-pip_8.1.2.bb > b/meta-python/recipes-devtools/python/python3-pip_8.1.2.bb > new file mode 100644 > index 0000000..612ba7d > --- /dev/null > +++ b/meta-python/recipes-devtools/python/python3-pip_8.1.2.bb > @@ -0,0 +1,13 @@ > +SUMMARY = "PIP is a tool for installing and managing Python packages" > +LICENSE = "MIT & LGPL-2.1" > +LIC_FILES_CHKSUM = > "file://LICENSE.txt;md5=25fba45109565f87de20bae85bc39452" > + > +SRC_URI[md5sum] = "87083c0b9867963b29f7aba3613e8f4a" > +SRC_URI[sha256sum] = > "4d24b03ffa67638a3fa931c09fd9e0273ffa904e95ebebe7d4b1a54c93d7b732" > + > +inherit pypi setuptools3 > + > +# Since PIP is like CPAN for PERL we need to drag in all python modules > to ensure everything works > +RDEPENDS_${PN} = "python3-modules python3-setuptools" > + > +BBCLASSEXTEND = "nativesdk" > -- > 2.8.3 > > -- > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
