Clearly an empty dir seems to be sub-optimal design, but if one would
need it, I'd recommend to add a pkg_postinst_${PN} script and
dynamically determine at installation time if this path needs to be
created or not.
So the dir either will be create by ${PN}-bin or by the script - I think
I've seen at a couple of times like that
On 14.12.20 18:46, Robert P. J. Day wrote:
On Mon, 14 Dec 2020, Peter Kjellerstedt wrote:
Say we have a recipe that creates an empty /etc/foo directory. Now we
want to add a new file in that directory /etc/foo/bar and package it as
${PN}-bar. This means the creation of the /etc/foo directory is moved
from the ${PN} package to the ${PN}-bar package. Is there any way to
make ${PN} continue to create an empty /etc/foo, or is the only
alternative to introduce an /etc/foo/.dummy and package it in ${PN}?
it strikes me that creating an empty directory for no other reason
than creating an empty directory is less-than-optimal design. the
proper approach is that all file installation should create
directories as needed.
rday
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#145607):
https://lists.openembedded.org/g/openembedded-core/message/145607
Mute This Topic: https://lists.openembedded.org/mt/78956546/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
