Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: isn't "do_install_append_pn-uclibc" partly redundant? [NEVER MIND]
Date: Thu, 16 Oct 2014 08:57:56 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1410160856580.6180@localhost> (raw)
In-Reply-To: <alpine.LFD.2.11.1410160850380.6082@localhost>

On Thu, 16 Oct 2014, Robert P. J. Day wrote:

>
>   perusing recipes for my courseware and ran across this in the listed
> file:
>
> meta/recipes-core/uclibc/uclibc.inc:do_install_append_pn-uclibc () {
>
> now, given that the above file is clearly the general include file for
> the uclibc package, could the task append definition:
>
>   do_install_append_pn-uclibc () {
>
> not have been written more simply as:
>
>   do_install_append () {
>
> as in, given that this task append is clearly only for the uclibc
> package, it seems unnecessary to add a package-specific override. most
> other recipes use the second, shorter form, so i was wondering if
> there was something subtle about the uclibc recipe that necessitated
> the first form.

  oh, wait, i just saw the associated recipe for uclibc-initial, so
the package-specific override in the .inc file for just the uclibc
package now makes sense.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



  reply	other threads:[~2014-10-16 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 15:54 isn't "do_install_append_pn-uclibc" partly redundant? Robert P. J. Day
2014-10-16 15:57 ` Robert P. J. Day [this message]
2014-10-16 16:04 ` Christopher Larson

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=alpine.LFD.2.11.1410160856580.6180@localhost \
    --to=rpjday@crashcourse.ca \
    --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