package.bbclass: make unshipped files
A message that is not in the archive (sent off-list or not yet received): mailman.11719.1316631917.14568.openembedded-core@lists.openembedded.org
Quoted 10 lines
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_installtask, 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).
Dan Lazzari Jr.
Firmware Engineer
[email protected]
Op 21 sep. 2011, om 21:10 heeft Daniel Lazzari het volgende geschreven:
Quoted 11 lines
Quoted 10 lines
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_installtask, 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.
Quoted 2 lines
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).
do_install_append() {
rm file1 file2 file3
}
Quoted 11 lines · Daniel Lazzari
Quoted 10 lines
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_installtask, 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.
Quoted 3 lines
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?
Quoted 7 lines
Dan Lazzari Jr.
Firmware Engineer
[email protected]
Signature · 2 lines
With best wishes Dmitry
Quoted 30 lines · Daniel Lazzari
Quoted 2 lines
Quoted 2 lines
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
Quoted 2 lines
Quoted 2 lines
files are generated by
do_installtask, which aren't necessary for our target systems. However in generic I think this is a very importantand
Quoted 1 line
Quoted 1 line
usually overlooked QA sign. E.g. recently I've found/fixed some bugs
in
Quoted 7 lines
Quoted 5 lines
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
Quoted 1 line
basis? I have a few internal projects whose normal build process spits
out
Quoted 1 line
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.
Quoted 8 lines
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?
--
With best wishes
Dmitry
Yeah, I freely admit that some of the project builds over here have some problems with what gets installed versus just built. The do_install_append suggestion seems like a workable solution. And just for the record, I like the idea of making this a fatal error.
Dan Lazzari Jr.
Firmware Engineer
[email protected]
Quoted 35 lines · Daniel Lazzari
Quoted 35 lines · Daniel Lazzari
Quoted 2 lines
Quoted 2 lines
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
Quoted 2 lines
Quoted 2 lines
files are generated by
do_installtask, which aren't necessary for our target systems. However in generic I think this is a very importantand
Quoted 1 line
Quoted 1 line
usually overlooked QA sign. E.g. recently I've found/fixed some bugs
in
Quoted 7 lines
Quoted 5 lines
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
Quoted 1 line
basis? I have a few internal projects whose normal build process spits
out
Quoted 1 line
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?
Quoted 8 lines
Quoted 3 lines
--
With best wishes
DmitryYeah, I freely admit that some of the project builds over here have some problems with what gets installed versus just built. The
do_install_appendsuggestion seems like a workable solution. And just for the record, I like the idea of making this a fatal error.
Thanks!
Quoted 6 lines
Dan Lazzari Jr.
Firmware Engineer
[email protected]
Signature · 2 lines
With best wishes Dmitry