The most common way what i have seen is to make a bbappend and
move/rename/remove/override the file.
The same situation exists dealing with config files like by connman.
Greetz
hka
Bernd Bauer <bernd.bauer@xxxxxx> schrieb am Mo., 13. Jän. 2020, 17:48:
Hi Andreas!
Without having tested it now, I can think of 3 possible solutions.
1) Add an "install_append" function to your recipe. As far as I
know, this overwrite lock does not apply here.
2) Add an apache_%.bbappend file in which you delete the
index.html file.
3) Maybe there is already a mechanism (variable) in the Apache
recipe that can replace the index file.
Greets Bernd
Am 13.01.20 um 12:02 schrieb DI Andreas Auer:
Hello.complaining.
I would like to integrate the "installation" of a website in Yocto. My
preferred way would be to have a new recipe which clones my GIT repo
containing the HTML files and installs them in the Yocto image.
The "problem" is that when I install my HTML files, I'm overwriting the
original index.html file provided by the apache recipe. And when I
overwrite a file which is provided by another recipe, Yocto is
it?
I know, it would be possible to write a bbappend file for the apache
recipe to integrate my website. But I think it would be better to have
this separated (website and webserver).
So, question is: Is it possible to change/overwrite files which are
provided by another recipe in a way that Yocto is not complaining about
BR
Andreas
--
| |O| | Bauer Bernd
| | |O| Sicher ist vi benutzerfreundlich,
|O|O|O| es ist nur eigen in der Wahl seiner Freunde.
