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:38:46 -0600 [thread overview]
Message-ID: <4EC562C6.8000905@windriver.com> (raw)
In-Reply-To: <1321521168.1264.43.camel@localhost.localdomain>
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.
--Mark
> On Thu, 2011-11-17 at 16:57 +0800, Henning Heinold wrote:
>> On Thu, Nov 17, 2011 at 08:14:06AM +0000, McClintock Matthew-B29882 wrote:
>>> On Wed, Nov 16, 2011 at 8:29 PM, Ni Qingliang
>>> <niqingliang@insigma.com.cn> wrote:
>>>> Hello, All:
>>>> I'm working on opensaf, wrote a bb file for it,
>>>> and found that the FILES_${PN} has included /usr/lib/${PN}/*.
>>>> but there are some .a and .so(symlink) in /usr/lib/${PN}, which will
>>>> result QA issue.
>>>> how to exclude some files (e.g. *.a, *.so) in FILES_${PN}?
>>>>
>>>> there are some elf in /usr/lib/${PN} whose prefix is not 'lib', so if
>>>> no 'exclude' feature, I must redefine FILES_${PN} like this:
>>>> FILES_${PN} = "/usr/lib/${PN}/*.so.* \
>>>> /usr/lib/${PN}/saf* \
>>>> /usr/lib/${PN}/open* \
>>>> /usr/lib/${PN}/immload \
>>>> /usr/lib/${PN}/nid_tipc \
>>>> /usr/lib/${PN}/smf* \
>>>> /usr/lib/${PN}/clc-cli/*"
>>>
>>> Explicitly list what you want in FILES_${PN}
>>>
>>> FILES_${PN} = /usr/lib/${PN}/saf
>>>
>>> Make another PACKAGE for other files
>>>
>>> PACKAGES =+ ${PN}-misc
>>> FILES_${PN}-misc = /usr/lib/${PN}/saf
>>>
>>> Maybe someone else can chime in if there is a way to mask certain files...
>>
>> No,
>>
>> QA would always complain. For all files you do not want to package make a do_install_append()
>> and remove them inside this function.
>>
>> Another solution would be to tweak the buildsystem of the software, not to install the unwanted
>> files.
>>
>> Bye Henning
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-11-17 19:45 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 [this message]
2011-11-17 19:43 ` Chris Larson
2011-11-17 19:51 ` Mark Hatle
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=4EC562C6.8000905@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