All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: poky@yoctoproject.org
Subject: Re: Files missing from package
Date: Mon, 08 Oct 2012 16:22:09 -0600	[thread overview]
Message-ID: <50735211.1090100@mlbassoc.com> (raw)
In-Reply-To: <1349728637.15658.127.camel@ted>

On 2012-10-08 14:37, Richard Purdie wrote:
> On Mon, 2012-10-08 at 18:40 +0100, Tomas Frydrych wrote:
>> On 08/10/12 17:24, Paul Eggleton wrote:
>>> Since ${sysconfdir} is /etc by default and ${sysconfdir} is in the default
>>> value of FILES_${PN}, and your additional package is appended to PACKAGES, I
>>> suspect you'll find the file is being picked up by the main package first. You
>>> need to use =+ instead of += so that the some-tool-tools package is prepended
>>> to PACKAGES and thus gets the file before the main package.
>>
>> Probably worth noting that using =+ with PACKAGES can have some
>> undesirable side effects. For example, if the recipe in question
>> generates packages dynamically, e.g., for plugins, the first package in
>> the PACKAGES list will be considered the 'main' package, and the dynamic
>> packages will RDEPEND on it. If you modify PACKAGES in such a recipe
>> using the =+, this will result in broken dependency chain without any
>> obvious signs something is not right. I think it's much better to
>> explicitly specify what should go into the main package than using =+ to
>> work around the unsuitable main package default.
>
> FWIW, there is the PACKAGE_BEFORE_PN variable for this and other
> scenarios where you want something just before PN in PACKAGES.

This does sound better, I always like to be explicit, especially when
the default/background has a possibility of biting me!

So, how would I use that for my case (i.e. what lines do I add/change
in my recipe to use it)?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2012-10-08 22:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 16:13 Files missing from package Gary Thomas
2012-10-08 16:24 ` Paul Eggleton
2012-10-08 16:32   ` Gary Thomas
2012-10-08 17:40   ` Tomas Frydrych
2012-10-08 18:22     ` Paul Eggleton
2012-10-08 18:56       ` Tomas Frydrych
2012-10-08 20:37     ` Richard Purdie
2012-10-08 22:22       ` Gary Thomas [this message]
2012-10-08 22:39         ` Richard Purdie
2012-10-09 12:36           ` Gary Thomas
2012-10-09 12:41             ` Paul Eggleton
2012-10-09 12:46               ` Gary Thomas
2012-10-09 12:48                 ` Paul Eggleton
2012-10-09 12:53                   ` Gary Thomas

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=50735211.1090100@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@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.