All of lore.kernel.org
 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 1/1] insane.bbclass: Added QA test for expanded ${D}
Date: Tue, 13 Jan 2015 16:49:39 -0600	[thread overview]
Message-ID: <54B5A103.4000201@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZ+j_=yrHQNAWUkjYyvg9P5BZFLZ-4YhPDLHgnqFBtJ-w@mail.gmail.com>

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

Thank Ross, sending new patch soon.
On 07/01/15 12:27, Burton, Ross wrote:
> Hi Alejandro,
>
> Looks good, but some small points:
>
> On 11 December 2014 at 22:40, Alejandro Hernandez 
> <alejandro.hernandez@linux.intel.com 
> <mailto:alejandro.hernandez@linux.intel.com>> wrote:
>
>     -           version-going-backwards \
>     +            version-going-backwards expanded_d \
>
>     +QAPATHTEST[expanded_d] = "package_qa_check_expanded_d"
>
>
> Rename this to expanded-d for consistency with the other symbols that 
> use - instead of _.
>
>     +           # Variables are actually var_${PN}
>
>
> No need to document idioms, remove this comment.
>
>     +                       messages["expanded_d"] = "FILES should not
>     contain the ${D} variable as it references the local build
>     directory not the target filesystem, best solution is to remove
>     the ${D} reference"
>
>
> This doesn't name the package which makes it tricky to find in large 
> builds.
>
> Ross
>


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

  reply	other threads:[~2015-01-13 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1418337489.git.alejandro.hernandez@linux.intel.com>
2014-12-11 22:40 ` [PATCH 1/1] insane.bbclass: Added QA test for expanded ${D} Alejandro Hernandez
2015-01-07 18:27   ` Burton, Ross
2015-01-13 22:49     ` Alejandro Hernandez [this message]
2015-01-07 22:02   ` Randy Witt
2015-01-07 23:04     ` Burton, Ross

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=54B5A103.4000201@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 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.