From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Greylist: delayed 406 seconds by postgrey-1.34 at layers.openembedded.org; Thu, 16 Oct 2014 16:04:48 UTC Received: from smtp685.redcondor.net (smtp685.redcondor.net [208.80.206.85]) by mail.openembedded.org (Postfix) with ESMTP id 65766716A3 for ; Thu, 16 Oct 2014 16:04:48 +0000 (UTC) Received: from astoria.ccjclearline.com ([64.235.106.9]) by smtp685.redcondor.net ({20c8e40f-6b6c-4c9e-abff-1640ea7bf404}) via TCP (outbound) with ESMTPS id 20141016155803419 for ; Thu, 16 Oct 2014 15:58:03 +0000 X-RC-FROM: X-RC-RCPT: Received: from [128.107.239.234] (port=42993 helo=crashcourse.ca) by astoria.ccjclearline.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1XenRH-00043H-4t for openembedded-core@lists.openembedded.org; Thu, 16 Oct 2014 11:58:07 -0400 Date: Thu, 16 Oct 2014 08:57:56 -0700 (PDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost To: OE Core mailing list In-Reply-To: Message-ID: References: User-Agent: Alpine 2.11 (LFD 23 2013-08-11) MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - astoria.ccjclearline.com X-AntiAbuse: Original Domain - lists.openembedded.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: X-MAG-OUTBOUND: ccj.redcondor.net@64.235.106.9/32 Subject: Re: isn't "do_install_append_pn-uclibc" partly redundant? [NEVER MIND] X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 16:04:49 -0000 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 ========================================================================