All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Martinovic <alan.martinovic@senic.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: CONFFILES journey form source dir to rootfs
Date: Mon, 12 Nov 2018 15:32:45 +0100	[thread overview]
Message-ID: <CAOT_U5bPpZ4rWUN=2cF5NS5fs08S5i80iJy60Lx=ZB_OpyrDVg@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0Lbnde9NX7XYGzD2UU78-R6bCjN8RvRPMvomYDnnV66sgQ@mail.gmail.com>

> The standard do_install (which calls make install) copies the file
> from the source tree to the staging directory.

What's the reason for not seeing that in `bitbake -e systemd`?


Be Well,
Alan

On Mon, Nov 12, 2018 at 1:30 PM Burton, Ross <ross.burton@intel.com> wrote:
>
> The standard do_install (which calls make install) copies the file
> from the source tree to the staging directory.
>
> Ross
> On Mon, 12 Nov 2018 at 11:52, Alan Martinovic <alan.martinovic@senic.com> wrote:
> >
> > Hi,
> > I'm trying to understand how a conf file finds its way from source to
> > the rootfs.
> >
> > The example is use is `journald.conf` from systemd.
> > The file originates from systemd source:
> >     work/cortexa7hf-neon-vfpv4-senic-linux-gnueabi/systemd/1_234-r0/git/src/journal/journald.conf
> >
> > In the environment is only mentioned as a part of the CONFFILES.
> > [output of `bitbake systemd -e` formated for readability]:
> >
> >     # $CONFFILES [2 operations]
> >     #   set /mnt/data/alan/work/senic-os/oe/meta/conf/documentation.conf:116
> >     #     [doc] "Identifies editable or configurable files that are
> > part of a package."
> >     #   override[systemd]:rename from CONFFILES_${PN} data.py:116 [expandKeys]
> >     #     "${sysconfdir}/machine-id
> >            ${sysconfdir}/systemd/coredump.conf
> >            ${sysconfdir}/systemd/journald.conf
> >            ${sysconfdir}/systemd/logind.conf
> >            ${sysconfdir}/systemd/system.conf
> >            ${sysconfdir}/systemd/user.conf"
> >     # pre-expansion value:
> >     #   "None"
> >     #
> >     # $CONFFILES_systemd
> >     #   rename from CONFFILES_${PN} data.py:116 [expandKeys]
> >     #     "${sysconfdir}/machine-id
> >            ${sysconfdir}/systemd/coredump.conf
> >            ${sysconfdir}/systemd/journald.conf
> >            ${sysconfdir}/systemd/logind.conf
> >            ${sysconfdir}/systemd/system.conf
> >            ${sysconfdir}/systemd/user.conf"
> >     CONFFILES_systemd="/etc/machine-id
> >             /etc/systemd/coredump.conf
> >             /etc/systemd/journald.conf
> >             /etc/systemd/logind.conf
> >             /etc/systemd/system.conf
> >             /etc/systemd/user.conf"
> >
> >
> > The file successfully ends up at `/etc/systemd/journald.conf`.
> >
> > Why isn't there an action in the environment showing the copying of
> > journald.conf
> > from `...git/src/journal/journald.conf` to
> > `${sysconfdir}/systemd/journald.conf`?
> >
> >
> > Disclaimer:
> > There were also some sed related actions with the file in the environment
> > which I dropped to reduce noise.
> >
> > Be Well,
> > Alan
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto


  reply	other threads:[~2018-11-12 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 11:52 CONFFILES journey form source dir to rootfs Alan Martinovic
2018-11-12 12:30 ` Burton, Ross
2018-11-12 14:32   ` Alan Martinovic [this message]
2018-11-12 15:38     ` Burton, Ross

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='CAOT_U5bPpZ4rWUN=2cF5NS5fs08S5i80iJy60Lx=ZB_OpyrDVg@mail.gmail.com' \
    --to=alan.martinovic@senic.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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 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.