From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: FILES_${PN} packaging and wildcarded exclusions
Date: Tue, 04 Mar 2014 11:05:34 +0000 [thread overview]
Message-ID: <5315B37E.9040505@dynamicdevices.co.uk> (raw)
In-Reply-To: <3478033.4G0PVG1MHp@peggleto-mobl5.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2807 bytes --]
On 04/03/2014 11:01, Paul Eggleton wrote:
> Hi Alex,
>
> On Tuesday 04 March 2014 10:10:13 Alex J Lennon wrote:
>> I'm trying to understand how to cleanly extend FILES${PN} to include
>> files that are staged and need to be packaged
>>
>> If I start with something like
>>
>> FILES_${PN} += " \
>> ${libdir}/mono/gac/policy.0.2.Mono.Addins/0.0.0.0__0738eb9f132ed756/* \
>> ${libdir}/mono/gac/policy.0.2.Mono.Addins.Setup/0.0.0.0__0738eb9f132ed756/*
>> \
>> ${libdir}/mono/gac/policy.0.6.Mono.Addins.CecilReflector/0.0.0.0__0738eb9f13
>> 2ed756/* \
>> ${libdir}/mono/gac/policy.0.6.Mono.Addins.Gui/0.0.0.0__0738eb9f132ed756/* \
>> <snip/>
>>
>> I seem to be able to clean that up a bit to
>>
>> FILES_${PN} += " \
>> ${libdir}/mono/gac/*/*/* \
>> <snip/>
>>
>> What I'd like to do is to be able to represent "all files excepting
>> files ending with .mdb", for example, as I want to add those to a
>> ${PN}-dbg package.
>>
>> I was wondering if there's a syntax I can use within FILES_${PN} to
>> achieve that cleanly?
> There isn't I'm afraid - the tools you have available are wildcards and the
> ordering of PACKAGES, since the first package whose FILES value matches a file
> will get the file. However, for this specific case this should be just fine -
> ${PN}-dbg appears before ${PN} in the default value of PACKAGES, so you just
> need to ensure FILES_${PN}-dbg is extended as needed.
Oh great, thanks. So as long as I make sure the order of precedence is
as needed in PACKAGES then the files will go in the right packages.
I wonder if there's any benefit to allowing regexp in FILES_
definitions? Or if that's just overcomplicating something that already
works?
> Cheers,
> Paul
>
--
Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>
Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA
mobile: +44 (0)7956 668178
Linkedin <http://www.linkedin.com/in/alexjlennon> Skype
<skype:alexjlennon?add>
This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended
recipient(s). Any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is prohibited. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, or contain viruses.
Anyone who communicates with us by e-mail is deemed to have accepted
these risks. Company Name is not responsible for errors or omissions in
this message and denies any responsibility for any damage arising from
the use of e-mail. Any opinion and other statement contained in this
message and any attachment are solely those of the author and do not
necessarily represent those of the company.
[-- Attachment #2.1: Type: text/html, Size: 5227 bytes --]
[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]
[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]
[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]
next prev parent reply other threads:[~2014-03-04 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 10:10 FILES_${PN} packaging and wildcarded exclusions Alex J Lennon
2014-03-04 11:01 ` Paul Eggleton
2014-03-04 11:05 ` Alex J Lennon [this message]
2014-03-04 11:14 ` Paul Eggleton
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=5315B37E.9040505@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=paul.eggleton@linux.intel.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.