All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Fred Ollinger <Fred.Ollinger@seescan.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: FILESEXTRAPATHS_prepend fails for systemd
Date: Fri, 2 Oct 2015 18:37:17 +0200	[thread overview]
Message-ID: <20151002163717.GB2386@jama> (raw)
In-Reply-To: <1443801396017.79471@seescan.com>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On Fri, Oct 02, 2015 at 03:58:04PM +0000, Fred Ollinger wrote:
> I'm trying to change my /etc/systemd/journald.conf file.
> 
> 
> I have created a file in:
> 
> 
> our_system/recipe-core/systemd_%.bbappend
> 
> 
> With the contents:
> 
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

This works only for files listed in SRC_URI, that's not the case for
journald.conf which is included directly in systemd sources.

> 
> I created a directory in the same path called "systemd" and placed our new version of journald.conf in it.
> 
> Then I did:
> 
> bitbake -c cleanall systemd && bitbake systemd
> bitbake -c cleanall our_image && bitbake our_image
> 
> Then I checked and the old journald.conf is still installed.
> 
> What am I doing wrong?
> 
> Frederick
> 
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-10-02 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 15:58 FILESEXTRAPATHS_prepend fails for systemd Fred Ollinger
2015-10-02 16:37 ` Martin Jansa [this message]
2015-10-02 16:44 ` Christopher Larson
2015-10-02 17:26   ` Daniel.
2015-10-02 18:11     ` Daniel.
2015-10-02 18:21       ` Christopher Larson
2015-10-02 18:22         ` Daniel.
2015-10-02 18:24           ` Christopher Larson
2015-10-02 18:26             ` Daniel.

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=20151002163717.GB2386@jama \
    --to=martin.jansa@gmail.com \
    --cc=Fred.Ollinger@seescan.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.