From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 0D233E00C97; Fri, 1 Apr 2016 05:35:19 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [95.211.233.247 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mx5-01.smtp.antispamcloud.com (mx5-01.smtp.antispamcloud.com [95.211.233.247]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B2692E00C92 for ; Fri, 1 Apr 2016 05:35:12 -0700 (PDT) Received: from 100-208.ftth.onsbrabantnet.nl ([88.159.208.100] helo=TOP-EX01.TOPIC.LOCAL) by mx5.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1alyHz-0000pC-GW; Fri, 01 Apr 2016 14:35:11 +0200 Received: from [192.168.80.121] (192.168.80.121) by TOP-EX01.TOPIC.LOCAL (192.168.10.102) with Microsoft SMTP Server id 14.3.224.2; Fri, 1 Apr 2016 14:34:58 +0200 To: Isak Lichtenstein , "yocto@yoctoproject.org" References: <91B4C1B91AAEFD42AC985EA0F3D4E6680194828956@kihagwinex01.int.kistler.com> From: Mike Looijmans Organization: TOPIC Message-ID: <56FE6AF2.4020508@topic.nl> Date: Fri, 1 Apr 2016 14:34:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <91B4C1B91AAEFD42AC985EA0F3D4E6680194828956@kihagwinex01.int.kistler.com> X-Originating-IP: [192.168.80.121] X-EXCLAIMER-MD-CONFIG: 9833cda7-5b21-4d34-9a38-8d025ddc3664 X-EXCLAIMER-MD-BIFURCATION-INSTANCE: 0 X-Filter-ID: s0sct1PQhAABKnZB5plbIbbvfIHzQjPVmPLZeVYSu3xU9luQrU+8/8qthi+0Jd/W6KAUC/fjyuDn NXFr4uarwxJ0Zj8PTNpPbeaBvR43hcK0Lu1/pfgJnj0z/TuzMbLhNASIqc7bioT75HeI3MixFcJp hFKEtikJ8+mEAuMVEz4GgzZY0B8aK/437BOssB4wrTYpRPI0yAnEAseAyt9DsFcU85NwBZhpHtLJ lWZW4vox6oLkxdolf7+6NMA8XBupHHASJNUmoOHSoqgqxfHmWWg2yYjjORmmN0LyAe5tAYN2i6Kl jC+UJ0r+QNiksHtPi926F9lLOeAHfox5zu0iL7nBOhVR8vaEHFS4lXg6GnZg/oUY21gm0RMu5MLF LPTkVV/WPW3BlGlmY1493zIPojphuv+eIM2u6uWWtABbM+hRca7B9GgeozLat2kP+jtovVKcHRkJ YLAwAzy3rqhRsDuCNsFU7KGw5GYMysh718RQr53GHarrOHZ706RqO53yf48w+JmMpKNnVU1HvK/K V2SdEOMftBjsWb6BDQzjSsFn/WkZPOZnSoXRj+EH9P0GLjJcjfxE0/g+NMmc87/ebLnshQ21myZi Vl7ZOsQ8f8jrWFmB1ndQl++MAWVSPZ82T19nVfDF7H5YJnmjNhKTYgEiRQv+PVjjwa+Z5RFCOMQs 8sTwUhuxZTlaVwv6bITolm5PSG9JIYSzz6XuENc/gUwhDWLqGoO0kypCQF4tov51qDGdQNm4hshX 90iD6g7s X-Report-Abuse-To: spam@mx99.antispamcloud.com X-Filter-Fingerprint: IFrWXGses7OKB5S5G8/dJXhXyDRoOQM5J3kcUr0HrMvJUWjZ8+qhjyB23tbDuyLOYL8Ff78gYsez 4Rl08xudmXi4esCQ0R1MchVjt7wblGlvhFgW0MjUMRkF5sMCDfftTXNFDzN17hnrWeZYOJvLq0Ic WjZ+XcEjj/7Pkld0zkmvziDInX9WdMov2kn2yXjdwv61T+KDYyYtREgszdyFwv8IxCB3p/oCKvxr eyISh3JGb7OS5oVgiO+kDxZrVPLz3MmEGC2PrUKqLq5WmHK+Nw== X-Originating-IP: 88.159.208.100 X-SpamExperts-Domain: topic.nl X-SpamExperts-Username: 88.159.208.100 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=88.159.208.100@topic.nl X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.00) X-Recommended-Action: accept Subject: Re: How to enforce installation of image specific config file/package X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2016 12:35:19 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable =EF=BB=BFOn 01-04-16 11:34, Isak Lichtenstein wrote: > Hi, > > I've got a package "A" that has a runtime dependency to a configuration f= ile. This configuration file is image specific. For each image I've got a s= pecific configuration package "config-image-X" that installs this needed co= nfiguration 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=20 dependency. Make the config package RDEPEND on "A". Images that install the= =20 config (which they have to do anyway according to your description) will th= en=20 automatically install "A" which at least accomplishes that you don't need t= o=20 specify both. I've been in the same position, and it just isn't possible to do what you w= ant. 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