From: "Konrad Weihmann" <kweihmann@outlook.com>
To: openembedded-core@lists.openembedded.org
Cc: peter.kjellerstedt@axis.com
Subject: Re: [OE-core] How to create a directory in multiple packages?
Date: Mon, 14 Dec 2020 19:20:42 +0100 [thread overview]
Message-ID: <AM9PR09MB473919AC57B98915E0E96A10A8C70@AM9PR09MB4739.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <f44dd44e-ac73-8ed-674e-d6f3cc289c@crashcourse.ca>
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
>
>
>
>
>
next prev parent reply other threads:[~2020-12-14 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 17:43 How to create a directory in multiple packages? Peter Kjellerstedt
2020-12-14 17:46 ` [OE-core] " Robert P. J. Day
2020-12-14 18:20 ` Konrad Weihmann [this message]
2020-12-15 1:01 ` Mark Hatle
2020-12-15 14:24 ` Peter Kjellerstedt
2020-12-15 22:05 ` Mark Hatle
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=AM9PR09MB473919AC57B98915E0E96A10A8C70@AM9PR09MB4739.eurprd09.prod.outlook.com \
--to=kweihmann@outlook.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.