Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] python3: Restructure python3 packaging and replace it with autopackaging
Date: Fri, 24 Nov 2017 17:50:46 -0600	[thread overview]
Message-ID: <8d583189-724f-e88a-1a65-628b5cfa2269@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZ9zc9iUDvqT0an2LFgNszckm2PKkTD__XQZ253YoeOrw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

Hey Ross,


The thing is that we do need them on the native sysroot, since when we 
are creating a new manifest, it uses python-native to do that, and it 
needs to match those files, if they dont exist, they end up in another 
package.


Alejandro


On 11/24/2017 11:05 AM, Burton, Ross wrote:
> On 18 October 2017 at 22:07, Alejandro Hernandez 
> <alejandro.hernandez@linux.intel.com 
> <mailto:alejandro.hernandez@linux.intel.com>> wrote:
>
>     @@ -77,8 +75,30 @@ do_install() {
>                     sed -i -e '1s|^#!.*|#!/usr/bin/env python3|'
>     $PYTHSCRIPT
>             done
>
>     -       # Tests are large and we don't need them in the native sysroot
>     -       rm ${D}${libdir}/python${PYTHON_MAJMIN}/test -rf
>     +        # Add a symlink to the native Python so that scripts can
>     just invoke
>     +        # "nativepython" and get the right one without needing
>     absolute paths
>     +        # (these often end up too long for the #! parser in the
>     kernel as the
>     +        # buffer is 128 bytes long).
>     +        ln -s python3-native/python3 ${D}${bindir}/nativepython3
>
>
> Is that rm of the tests redundant?
>
> Ross
>


[-- Attachment #2: Type: text/html, Size: 2511 bytes --]

  reply	other threads:[~2017-11-24 23:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 21:07 [PATCH 0/4] Restructure python2 and python3 packaging system Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 1/4] python: Restructure python packaging and replace it with autopackaging Alejandro Hernandez
2017-11-24 16:57   ` Burton, Ross
2017-11-24 23:49     ` Alejandro Hernandez
2017-11-24 17:06   ` Burton, Ross
2017-11-24 23:51     ` Alejandro Hernandez
2017-11-25  5:04       ` Tim Orling
2017-11-25 23:45         ` Alejandro Hernandez
2017-11-26  2:08           ` Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 2/4] python3: Restructure python3 " Alejandro Hernandez
2017-11-24 17:05   ` Burton, Ross
2017-11-24 23:50     ` Alejandro Hernandez [this message]
2017-10-18 21:07 ` [PATCH 3/4] python3: fix RDEPENDS on several recipes, due to non-existent python3 packages Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 4/4] hwlatdetect: fix RDEPENDS to avoid QA failures Alejandro Hernandez
2017-10-19 20:14 ` ✗ patchtest: failure for Restructure python2 and python3 packaging system (rev2) Patchwork
2017-10-19 20:34   ` Leonardo Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8d583189-724f-e88a-1a65-628b5cfa2269@linux.intel.com \
    --to=alejandro.hernandez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox