Re: [yocto] What's up with python3
On 8 June 2017 at 13:10, Gary Thomas wrote: > What would I lose by do this, in general, as it's pretty obvious > that python3 is not needed by any of the recipes I use? > It's the scripts in opkg-utils, so if you're not installing that in your image then you won't notice at all. (looks like the recipe should respect the python PACKAGECONFIG and delete the python scripts so they can't get packaged) Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What's up with python3
On 2017-06-08 13:52, Burton, Ross wrote: On 8 June 2017 at 08:28, Gary Thomas mailto:g...@mlbassoc.com>> wrote: I've listed all the recipes used in my build (from bitbake -g => recipe-depends.dot) and sucked out the ones that claim to depend on python3. I don't see why, for example, python(2) depends on python3? I'm 90% sure that this all comes through opkg-utils being the provider for update-alternatives. You could verify this by disabling the python PACKAGECONFIG in opkg-utils. I'm impressed! That eliminated all of them :-) What would I lose by do this, in general, as it's pretty obvious that python3 is not needed by any of the recipes I use? -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What's up with python3
On 8 June 2017 at 08:28, Gary Thomas wrote: > I've listed all the recipes used in my build (from bitbake -g => > recipe-depends.dot) > and sucked out the ones that claim to depend on python3. I don't see why, > for > example, python(2) depends on python3? > I'm 90% sure that this all comes through opkg-utils being the provider for update-alternatives. You could verify this by disabling the python PACKAGECONFIG in opkg-utils. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What's up with python3
On 2017-06-08 13:09, Alexander Kanavin wrote: On 06/08/2017 10:28 AM, Gary Thomas wrote: I'm building using Poky/Yocto master 576821ea0a7558b626ccc87e9ae0e9ee40864956 and I've noticed that python3 (target) is being built for my image, but it doesn't end up in the actual image. None of my own recipes mention python3 at all, yet virtually every recipe that's used in the build depend on it. I've listed all the recipes used in my build (from bitbake -g => recipe-depends.dot) and sucked out the ones that claim to depend on python3. I don't see why, for example, python(2) depends on python3? Can someone explain this? I've added the appropriate files to this email. I'm mostly curious, but also a bit concerned that my builds are doing more than they need (and hence just taking longer than they might need to) Typically for two reasons: a) a recipe needs to execute python during build, and host python is not suitable for some reason - so native python is built and used; Not that: I filtered out all uses of python3-native - these are only *target* dependencies b) a supplementary package needs python, while the main package does not - most often this is the -ptest package, which will not end up in the image, unless you ask. None of my recipes build -ptest stuff: $ find tmp/deploy/ipk/ -name "*ptest*" -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] What's up with python3
On 06/08/2017 10:28 AM, Gary Thomas wrote: I'm building using Poky/Yocto master 576821ea0a7558b626ccc87e9ae0e9ee40864956 and I've noticed that python3 (target) is being built for my image, but it doesn't end up in the actual image. None of my own recipes mention python3 at all, yet virtually every recipe that's used in the build depend on it. I've listed all the recipes used in my build (from bitbake -g => recipe-depends.dot) and sucked out the ones that claim to depend on python3. I don't see why, for example, python(2) depends on python3? Can someone explain this? I've added the appropriate files to this email. I'm mostly curious, but also a bit concerned that my builds are doing more than they need (and hence just taking longer than they might need to) Typically for two reasons: a) a recipe needs to execute python during build, and host python is not suitable for some reason - so native python is built and used; b) a supplementary package needs python, while the main package does not - most often this is the -ptest package, which will not end up in the image, unless you ask. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
