Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mariano Lopez <mariano.lopez@linux.intel.com>
To: Joshua G Lock <joshua.g.lock@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Allows to copy symlinks to DUTs with testimage
Date: Tue, 26 Jul 2016 12:35:37 -0500	[thread overview]
Message-ID: <57979F69.6080903@linux.intel.com> (raw)
In-Reply-To: <1469550475.2740.9.camel@linux.intel.com>



On 07/26/2016 11:27 AM, Joshua G Lock wrote:
> On Tue, 2016-07-26 at 07:39 +0000, mariano.lopez@linux.intel.com wrote:
>> From: Mariano Lopez <mariano.lopez@linux.intel.com>
>>
>> Currently when using the install functionality in the DUT without
>> package
>> manager, if you copy a symlink the function will fail.
>>
>> These series will change the behaviour and will allow to recreate the
>> symlinks in the DUT.
>>
>> [YOCTO #9932]
>
> Would oe.path.copytree() work instead of using shutil.copytree()?
> copytree() was added because shutil was quite slow for our usage.

I didn't know the existence of that function, I tried it and it can 
replace shutil.copytree(). I'll send a v2.

>
> Regards,
>
> Joshua

Mariano Lopez


      reply	other threads:[~2016-07-26 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26  7:39 [PATCH 0/3] Allows to copy symlinks to DUTs with testimage mariano.lopez
2016-07-26  7:39 ` [PATCH 1/3] oeqa/utils/commands.py: Add oeqa_copy function mariano.lopez
2016-07-26 16:13   ` Burton, Ross
2016-07-26 17:34     ` Mariano Lopez
2016-07-26  7:39 ` [PATCH 2/3] oeqa/oetest.py: Allow to export packages using symlinks mariano.lopez
2016-07-26  7:39 ` [PATCH 3/3] oeqa/utils/sshcontrol.py: Allows to copy symlinks to target mariano.lopez
2016-07-26 16:27 ` [PATCH 0/3] Allows to copy symlinks to DUTs with testimage Joshua G Lock
2016-07-26 17:35   ` Mariano Lopez [this message]

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=57979F69.6080903@linux.intel.com \
    --to=mariano.lopez@linux.intel.com \
    --cc=joshua.g.lock@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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