<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 11.09.2018 um 20:56 schrieb Alejandro Enedino Hernandez Samaniego <<a href="mailto:alejandro.enedino.hernandez-samaniego@xilinx.com" class="">alejandro.enedino.hernandez-samaniego@xilinx.com</a>>:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hey Jens,</p></div></div></blockquote><div>Hey <span style="caret-color: rgb(34, 34, 34); color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: small; background-color: rgb(255, 255, 255);" class="">Alejandro,</span></div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">
<div class="moz-cite-prefix">On 09/10/2018 11:58 PM, Jens Rehsack
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:0EC3E010-56C9-4EB4-90B4-FD9A68F99AAC@netbsd.org" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">Am 10.09.2018 um 23:33 schrieb Alejandro Enedino
Hernandez Samaniego <<a href="mailto:alejandro.enedino.hernandez-samaniego@xilinx.com" class="" moz-do-not-send="true">alejandro.enedino.hernandez-samaniego@xilinx.com</a>>:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hey Jens,</p><p class=""><br class="">
</p><p class="">As I explained before, when you create a
manifest for python (target), it uses the native build
as base (it literally runs the native python that was
just built), it is assumed its the same version as
target and contains all the modules provided by
upstream, otherwise the missing modules cannot be
checked for dependencies, and the manifest becomes
incoherent, so its not an option to have an incomplete
python native build.</p>
</div>
</div>
</blockquote>
<div class="">In that case, uuid for target never gets deployed, but it
is. And I didn't see any packaging issues for `python3` nor
for `nativesdk-python3`</div>
</div>
</blockquote>
<br class="">
<br class="">
I don't see what that has to do with anything, fixing the native
build should not affect what gets deployed on target, thats exactly
why we have a manifest, so they user can decide what to install and
what not to install.<br class=""></div></div></blockquote><div><br class=""></div><div>The manifest isn't used for python3-native.</div><div>You try to argue whether there is an error to be fixed - and I don't agree.</div><div>Each fix requires effort - and that's why some errors will never become fixed. When the impact is reasonable or high enough, fixes are more likely.</div><div><br class=""></div><div>So: before you try to force me into "that's all ugly und must be seriously beautified just because ..." I will not do anything.</div><div>When you give me a sane reason, I try to understand and make a decision.</div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">
I know you didn't see any packaging issues, but that doesn't mean
they don't exist, just from the log I showed you, I can tell you
that the python3-crypt package is not created correctly, for
example, if you do:<br class="">
<br class="">
IMAGE_INSTALL_append = " python3-crypt"<br class="">
<br class="">
Boot the image, run python3 and you try to import sha3, it will
fail, because the sha3*.so library won't be on the filesystem.<br class="">
<br class="">
<br class="">
And thats because the sha3.*.so library was just introduced in this
upgrade, and our manifest isn't aware it exists, hence it'll end up
on python3-misc and you have just created an unnecessary dependency
from python3-crypt to python3-misc (and worse, a dependency which
were not even aware of, until we test it manually), which beats the
whole purpose of the manifest.<br class="">
<br class="">
The do_package function is not gonna fail just because, so you won't
see errors, but the files will be packaged incorrectly, causing
runtime errors as a consequence, the create_manifest task tries to
solve these runtime issues before they happen.<br class=""></div></div></blockquote><div><br class=""></div><div>That's something completely different. I'm not a python guy and I don't get from the ChangeLog what I have to change in the manifest.</div><div>I can and will do such stuff when doing the perl update. For python, I ask for review because of things I don't know.</div><div><br class=""></div><div>You can give me a reasonable list of such changes and I update the manifest accordingly when I rebase the patch after Ross PGO patches are committed.</div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">
Cheers,<br class="">
<br class="">
Alejandro<br class="">
<br class="">
<br class="">
<blockquote type="cite" cite="mid:0EC3E010-56C9-4EB4-90B4-FD9A68F99AAC@netbsd.org" class="">
<div class="">
<blockquote type="cite" class="">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Yes you probably need a patch to look at the
correct directories for the h files, as well as a
dependency to make the h files available on
recipe-sysroot-native.</p>
</div>
</div>
</blockquote>
Please check the submission.</div>
</blockquote>
<br class="">
I did, its not checking inside recipe-sysroot-native.<br class=""></div></div></blockquote><div><br class=""></div><div>I know. You could check the submission anyway and find the right patch and then argue differently.</div></div><div class=""><br class=""></div>Cheers<br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-- </div><div class="">Jens Rehsack - <a href="mailto:rehsack@gmail.com" class="">rehsack@gmail.com</a></div></div></div>
</div>
<br class=""></body></html>