All of lore.kernel.org
 help / color / mirror / Atom feed
From: gmane@reliableembeddedsystems.com
To: Bill Randle <bill.randle@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Y-AB PublishArtifacts toolchain wrong dir
Date: Sun, 09 Oct 2016 08:28:16 -0500	[thread overview]
Message-ID: <1d2368a9693d7a4fcaa1f83edbbfb851@reliableembeddedsystems.com> (raw)
In-Reply-To: <CA+n--H_F3fo3_zEW=u_ySEXj+T3-7UWWy0Yw651JrvEfeCx2Lg@mail.gmail.com>

Hi,

On 2016-10-08 18:17, Bill Randle wrote:
> Hi,
> 
> I think I would leave the toolchain artifact as is, but just surround
> the the 'cp' with an 'if' statement. E.g.,:
>   if [ -e <path-to-x86-toolchain> ]; then
>     cp <cp-args> <path-to-x86-toolchain> <destination>;
>   fi;
>   if [ -e <path-to-x86_64-toolchain> ]; then
>     cp <cp-args> <path-to-x86_64-toolchain> <destination>;
>   fi;
> 

This sounds like a brilliant idea. It looks like now I have the 
behaviour of the good old Y-AB plus md5sums and friends and being copied 
over.
What do you think about this patch? [1]


>     -Bill
> 

[1] 
https://github.com/RobertBerger/autobuilder-patches/blob/master/before-install/0004-deal-only-with-built-toolchains-cp-also-md5-and-mani.patch

Regards,

Robert


  reply	other threads:[~2016-10-09 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:44 Y-AB PublishArtifacts toolchain wrong dir gmane
2016-10-08  3:05 ` Bill Randle
2016-10-08  6:10   ` gmane
2016-10-08  6:27   ` gmane
2016-10-08 14:28     ` Bill Randle
2016-10-08 21:52       ` gmane
2016-10-08 23:17         ` Bill Randle
2016-10-09 13:28           ` gmane [this message]
2016-10-09 14:44             ` Bill Randle

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=1d2368a9693d7a4fcaa1f83edbbfb851@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.com \
    --cc=bill.randle@gmail.com \
    --cc=yocto@yoctoproject.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 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.