On 9/21/11, Daniel Lazzari <dlazz...@leapfrog.com> wrote: >>I belive that "files were installed but not shipped in any package" >>message should become a fatal error. While it's true that sometimes some >>files are generated by do_install task, which aren't necessary for our >>target systems. However in generic I think this is a very important and >>usually overlooked QA sign. E.g. recently I've found/fixed some bugs in >>eglibc packaging only due to making this a fatal error. Sometimes new >>versions of a software add new files, but then they are sometimes >>ignored, as this messages can be easily missed. You can come with more >>examples if you'd like to. >> > > Could we have a variable that overrides this functionality on a per recipe > basis? I have a few internal projects whose normal build process spits out > files I'd rather not have to package in our oe recipes (like map files).
Of couse I can add it, but it might be simpler to use some other options: 1) do_install_append() with rm as Koen suggested 2) create a package with all map files that are created by your software. BTW, just to make sure that we understand each other: your software _installs_ map files and you don't want to package them, doesn't it? > > Dan Lazzari Jr. > Firmware Engineer > dlazz...@leapfrog.com > > > -- With best wishes Dmitry _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
