* [meta-python][PATCH] pycrypto: Add recipe to have support on python3
@ 2018-01-04 16:06 Ricardo Silva
2018-01-04 16:44 ` Tim Orling
0 siblings, 1 reply; 6+ messages in thread
From: Ricardo Silva @ 2018-01-04 16:06 UTC (permalink / raw)
To: openembedded-devel
The pycrypto module sources can be used for both python2 and python3,
but a recipe for python3 was missing, so add it.
Recipe is basically the same as for python2 (python-pycrypto_2.6.1.bb),
but using distutils3 instead.
Signed-off-by: Ricardo Silva <rjpdasilva@gmail.com>
---
.../recipes-devtools/python/python3-pycrypto_2.6.1.bb | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
diff --git a/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
new file mode 100644
index 000000000..2878c8599
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
@@ -0,0 +1,13 @@
+inherit distutils3
+require python-pycrypto.inc
+
+SRC_URI += "file://cross-compiling.patch \
+ file://CVE-2013-7459.patch \
+ "
+
+# We explicitly call distutils_do_install, since we want it to run, but
+# *don't* want the autotools install to run, since this package doesn't
+# provide a "make install" target.
+do_install() {
+ distutils3_do_install
+}
--
2.15.1
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [meta-python][PATCH] pycrypto: Add recipe to have support on python3
2018-01-04 16:06 [meta-python][PATCH] pycrypto: Add recipe to have support on python3 Ricardo Silva
@ 2018-01-04 16:44 ` Tim Orling
2018-01-04 16:51 ` Ricardo Silva
0 siblings, 1 reply; 6+ messages in thread
From: Tim Orling @ 2018-01-04 16:44 UTC (permalink / raw)
To: Ricardo Silva; +Cc: openembedded-devel
> On Jan 4, 2018, at 8:06 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>
> The pycrypto module sources can be used for both python2 and python3,
> but a recipe for python3 was missing, so add it.
>
> Recipe is basically the same as for python2 (python-pycrypto_2.6.1.bb),
> but using distutils3 instead.
>
> Signed-off-by: Ricardo Silva <rjpdasilva@gmail.com>
> ---
> .../recipes-devtools/python/python3-pycrypto_2.6.1.bb | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
> create mode 100644 meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
>
> diff --git a/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
> new file mode 100644
> index 000000000..2878c8599
> --- /dev/null
> +++ b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
> @@ -0,0 +1,13 @@
> +inherit distutils3
> +require python-pycrypto.inc
> +
> +SRC_URI += "file://cross-compiling.patch \
> + file://CVE-2013-7459.patch \
> +
These will not be picked up as they are in "python-pycrypto" directory (not in “files” or “python3-pycrypto”, etc.). This will result in a fetcher failure.
Rather than duplicate the SRC_URI in both python2- and python3- recipes, we should add them to python-pycrypto.inc and add the following to python-pycrypto.inc
FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
> "
> +
> +# We explicitly call distutils_do_install, since we want it to run, but
> +# *don't* want the autotools install to run, since this package doesn't
> +# provide a "make install" target.
> +do_install() {
> + distutils3_do_install
> +}
> --
> 2.15.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-python][PATCH] pycrypto: Add recipe to have support on python3
2018-01-04 16:44 ` Tim Orling
@ 2018-01-04 16:51 ` Ricardo Silva
2018-01-04 16:56 ` Tim Orling
0 siblings, 1 reply; 6+ messages in thread
From: Ricardo Silva @ 2018-01-04 16:51 UTC (permalink / raw)
To: Tim Orling; +Cc: openembedded-devel
Hi Tim,
Thanks for reviewing.
On 01/04/2018 04:44 PM, Tim Orling wrote:
>
>> On Jan 4, 2018, at 8:06 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>>
>> The pycrypto module sources can be used for both python2 and python3,
>> but a recipe for python3 was missing, so add it.
>>
>> Recipe is basically the same as for python2 (python-pycrypto_2.6.1.bb),
>> but using distutils3 instead.
>>
>> Signed-off-by: Ricardo Silva <rjpdasilva@gmail.com>
>> ---
>> .../recipes-devtools/python/python3-pycrypto_2.6.1.bb | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>> create mode 100644 meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
>>
>> diff --git a/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
>> new file mode 100644
>> index 000000000..2878c8599
>> --- /dev/null
>> +++ b/meta-python/recipes-devtools/python/python3-pycrypto_2.6.1.bb
>> @@ -0,0 +1,13 @@
>> +inherit distutils3
>> +require python-pycrypto.inc
>> +
>> +SRC_URI += "file://cross-compiling.patch \
>> + file://CVE-2013-7459.patch \
>> +
>
> These will not be picked up as they are in "python-pycrypto" directory (not in “files” or “python3-pycrypto”, etc.). This will result in a fetcher failure.
You're right.
I had a leftover files that made my tests pass. Should have tested with a clean tree.
>
> Rather than duplicate the SRC_URI in both python2- and python3- recipes, we should add them to python-pycrypto.inc and add the following to python-pycrypto.inc
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
>
Agree.
Shall I send a v2 with your suggested changes?
Regards,
Ricardo Silva
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-python][PATCH] pycrypto: Add recipe to have support on python3
2018-01-04 16:51 ` Ricardo Silva
@ 2018-01-04 16:56 ` Tim Orling
2018-01-04 17:27 ` Ricardo Silva
0 siblings, 1 reply; 6+ messages in thread
From: Tim Orling @ 2018-01-04 16:56 UTC (permalink / raw)
To: Ricardo Silva; +Cc: openembedded-devel
> On Jan 4, 2018, at 8:51 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>
>>
>> Rather than duplicate the SRC_URI in both python2- and python3- recipes, we should add them to python-pycrypto.inc and add the following to python-pycrypto.inc
>>
>> FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
>>
>
> Agree.
> Shall I send a v2 with your suggested changes?
>
Yes, please. If you don’t mind (it will need to remove the extra SRC_URI lines from python2 recipe, add the SRC_URI lines and FILESEXTRAPATHS to .inc and then add the python3 recipe).
> Regards,
>
> Ricardo Silva
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-python][PATCH] pycrypto: Add recipe to have support on python3
2018-01-04 16:56 ` Tim Orling
@ 2018-01-04 17:27 ` Ricardo Silva
2018-01-04 18:11 ` Tim Orling
0 siblings, 1 reply; 6+ messages in thread
From: Ricardo Silva @ 2018-01-04 17:27 UTC (permalink / raw)
To: Tim Orling; +Cc: openembedded-devel
Hi Tim,
On 01/04/2018 04:56 PM, Tim Orling wrote:
>
>> On Jan 4, 2018, at 8:51 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>>
>>>
>>> Rather than duplicate the SRC_URI in both python2- and python3- recipes, we should add them to python-pycrypto.inc and add the following to python-pycrypto.inc
>>>
>>> FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
>>>
>>
>> Agree.
>> Shall I send a v2 with your suggested changes?
>>
>
> Yes, please. If you don’t mind (it will need to remove the extra SRC_URI lines from python2 recipe, add the SRC_URI lines and FILESEXTRAPATHS to .inc and then add the python3 recipe).
Glad to. You mean the changes should be split over a patch series, or OK
to have a single patch with all the changes?
Also note that the .inc file already had :
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
so I would just change that to:
FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:"
Regards,
Ricardo Silva
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [meta-python][PATCH] pycrypto: Add recipe to have support on python3
2018-01-04 17:27 ` Ricardo Silva
@ 2018-01-04 18:11 ` Tim Orling
0 siblings, 0 replies; 6+ messages in thread
From: Tim Orling @ 2018-01-04 18:11 UTC (permalink / raw)
To: Ricardo Silva; +Cc: openembedded-devel
> On Jan 4, 2018, at 9:27 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>
> Hi Tim,
>
> On 01/04/2018 04:56 PM, Tim Orling wrote:
>>
>>> On Jan 4, 2018, at 8:51 AM, Ricardo Silva <rjpdasilva@gmail.com> wrote:
>>>
>>>>
>>>> Rather than duplicate the SRC_URI in both python2- and python3- recipes, we should add them to python-pycrypto.inc and add the following to python-pycrypto.inc
>>>>
>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
>>>>
>>>
>>> Agree.
>>> Shall I send a v2 with your suggested changes?
>>>
>>
>> Yes, please. If you don’t mind (it will need to remove the extra SRC_URI lines from python2 recipe, add the SRC_URI lines and FILESEXTRAPATHS to .inc and then add the python3 recipe).
>
> Glad to. You mean the changes should be split over a patch series, or OK
> to have a single patch with all the changes?
>
Single patch touching all three files is fine.
> Also note that the .inc file already had :
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> so I would just change that to:
> FILESEXTRAPATHS_prepend := "${THISDIR}/python-pycrypto:”
>
Correct. As ${PN} would resolve to python3-pycrypto and not work as intended :)
> Regards,
>
> Ricardo Silva
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-01-04 18:11 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-01-04 16:06 [meta-python][PATCH] pycrypto: Add recipe to have support on python3 Ricardo Silva
2018-01-04 16:44 ` Tim Orling
2018-01-04 16:51 ` Ricardo Silva
2018-01-04 16:56 ` Tim Orling
2018-01-04 17:27 ` Ricardo Silva
2018-01-04 18:11 ` Tim Orling
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.