From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: how to exclude files when packaging?
Date: Thu, 17 Nov 2011 13:51:57 -0600 [thread overview]
Message-ID: <4EC565DD.4070402@windriver.com> (raw)
In-Reply-To: <CABcZANmaGwMmKUkNoAg2C_nECa2AvXjfPYk_z-MA1Hj2YhW0Rg@mail.gmail.com>
On 11/17/11 1:43 PM, Chris Larson wrote:
> On Thu, Nov 17, 2011 at 12:38 PM, Mark Hatle<mark.hatle@windriver.com> wrote:
>> On 11/17/11 3:12 AM, Ni Qingliang wrote:
>>>
>>> I still think that the 'exclude" feature would be better.:)
>>
>> IMHO an exclude function would simply be an automated rm -f<list> at the
>> end of the install process.
>>
>> It should be fairly easy to implement this if someone thinks it's a better
>> idea then making individual recipes run a rm -f of their own.
>
> I wonder if, in general, it'd be useful to implement glob exclusions.
> In other words, our list of patterns could become more like a
> .gitignore file:
> /foo/*
> !/foo/bar
I considered that early on in the Yocto Project work -- but decided against it
due to simply the complications required to ensure that the patterns worked as
the end user expected them.
I know the bitbake back end and OE classes have matured since then, it may be
easier to implement now -- if so I'm certainly interested in this.
--Mark
next prev parent reply other threads:[~2011-11-17 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 2:29 how to exclude files when packaging? Ni Qingliang
2011-11-17 8:14 ` McClintock Matthew-B29882
2011-11-17 8:56 ` Martin Jansa
2011-11-17 8:57 ` Henning Heinold
2011-11-17 9:12 ` Ni Qingliang
2011-11-17 19:38 ` Mark Hatle
2011-11-17 19:43 ` Chris Larson
2011-11-17 19:51 ` Mark Hatle [this message]
2011-11-17 9:10 ` Koen Kooi
2011-11-17 9:30 ` Ni Qingliang
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=4EC565DD.4070402@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox