All of lore.kernel.org
 help / color / mirror / Atom feed
* CONFFILES journey form source dir to rootfs
@ 2018-11-12 11:52 Alan Martinovic
  2018-11-12 12:30 ` Burton, Ross
  0 siblings, 1 reply; 4+ messages in thread
From: Alan Martinovic @ 2018-11-12 11:52 UTC (permalink / raw)
  To: Yocto-mailing-list

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


^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: CONFFILES journey form source dir to rootfs
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Burton, Ross @ 2018-11-12 12:30 UTC (permalink / raw)
  To: Alan Martinovic; +Cc: Yocto-mailing-list

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


^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: CONFFILES journey form source dir to rootfs
  2018-11-12 12:30 ` Burton, Ross
@ 2018-11-12 14:32   ` Alan Martinovic
  2018-11-12 15:38     ` Burton, Ross
  0 siblings, 1 reply; 4+ messages in thread
From: Alan Martinovic @ 2018-11-12 14:32 UTC (permalink / raw)
  To: Burton, Ross; +Cc: Yocto-mailing-list

> 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


^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: CONFFILES journey form source dir to rootfs
  2018-11-12 14:32   ` Alan Martinovic
@ 2018-11-12 15:38     ` Burton, Ross
  0 siblings, 0 replies; 4+ messages in thread
From: Burton, Ross @ 2018-11-12 15:38 UTC (permalink / raw)
  To: Alan Martinovic; +Cc: Yocto-mailing-list

On Mon, 12 Nov 2018 at 14:33, Alan Martinovic <alan.martinovic@senic.com> wrote:
> > 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`?

It is there:

do_install() {
        meson_do_install
...
}

do_install calls meson_do_install which calls ninja install, which
copies the file from the build directory to the staging directory,
which is then used in packaging.

Ross


^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-11-12 15:38 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2018-11-12 15:38     ` Burton, Ross

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.