From: Mike Looijmans <mike.looijmans@topic.nl>
To: Isak Lichtenstein <Isak.Lichtenstein@kistler.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to enforce installation of image specific config file/package
Date: Fri, 1 Apr 2016 14:34:58 +0200 [thread overview]
Message-ID: <56FE6AF2.4020508@topic.nl> (raw)
In-Reply-To: <91B4C1B91AAEFD42AC985EA0F3D4E6680194828956@kihagwinex01.int.kistler.com>
On 01-04-16 11:34, Isak Lichtenstein wrote:
> Hi,
>
> I've got a package "A" that has a runtime dependency to a configuration file. This configuration file is image specific. For each image I've got a specific configuration package "config-image-X" that installs this needed configuration file and I build multiple image in the same build directory.
> How can I enforce that each image containing package "A" also installs an image specific configuration package?
If the "config" package is image-specific, you could just invert the
dependency. Make the config package RDEPEND on "A". Images that install the
config (which they have to do anyway according to your description) will then
automatically install "A" which at least accomplishes that you don't need to
specify both.
I've been in the same position, and it just isn't possible to do what you want.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
prev parent reply other threads:[~2016-04-01 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 9:34 How to enforce installation of image specific config file/package Isak Lichtenstein
2016-04-01 11:46 ` Esponde, Joel
2016-04-01 12:38 ` Isak Lichtenstein
2016-04-02 8:12 ` Khem Raj
2016-04-12 14:36 ` Isak Lichtenstein
2016-04-01 12:34 ` Mike Looijmans [this message]
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=56FE6AF2.4020508@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=Isak.Lichtenstein@kistler.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.