From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] How to create a directory in multiple packages?
Date: Mon, 14 Dec 2020 19:01:36 -0600 [thread overview]
Message-ID: <6df31263-e880-19a8-10ed-7ec6a8a2b5ba@kernel.crashing.org> (raw)
In-Reply-To: <9f740ac720f742ab869a15de54cf865e@XBOX03.axis.com>
On 12/14/20 11:43 AM, 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}?
try adjust the order of the PACKAGES variant. Something like:
PACKAGES = "${PN}-bar ... ${PN}"
FILES_${PN}-bar = "/etc/foo/bar"
FILES_${PN} = "/etc/foo"
That SHOULD package the file 'bar' in -bar, and the directory in ${PN}.
(Some of the people commenting this isn't less then optimal, actually it's not
that unusual.. Typical case I see is creating a directory in /var or /usr/share
for datafiles and the main package owns the directory, with sub-packages [or
other packages] contributing data into that directory.)
--Mark
> //Peter
>
>
>
>
>
next prev parent reply other threads:[~2020-12-15 1:01 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
2020-12-15 1:01 ` Mark Hatle [this message]
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=6df31263-e880-19a8-10ed-7ec6a8a2b5ba@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox