All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: seth bollinger <seth.boll@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Recipes that update a shared file
Date: Thu, 10 Oct 2013 10:31:45 +0100	[thread overview]
Message-ID: <2034055.AmVRsnPTrY@helios> (raw)
In-Reply-To: <5255F1CF.8020203@gmail.com>

Hi Seth,

On Wednesday 09 October 2013 19:16:15 seth bollinger wrote:
> What's the best practice for recipes that need to update a shared file
> provided by a different recipe?  For example let's say that the
> widget-watcher recipe creates /etc/ww.conf and the widget1, and widget2
> recipes need to append a line to the config.  I've searched through the
> recipes a bit and can't find a good example.  The closest that I've seen
> is pkg_postinst().  Is that the best method?

That's really the recommended way to do it. If the software being configured 
supports it, another way is to set it up to read all configuration files from a 
directory and then you can simply install a new file into that directory from 
the other recipe (e.g. Apache is usually configured to read all configuration 
files in /etc/httpd/conf.d or similar).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-10-10  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10  0:16 Recipes that update a shared file seth bollinger
2013-10-10  9:31 ` Paul Eggleton [this message]
2013-10-10 14:36   ` Seth Bollinger
2013-10-10 14:40     ` Burton, Ross
2013-10-10 15:02       ` Seth Bollinger
2013-10-10 15:09         ` Burton, Ross
2013-10-10 15:17           ` Seth Bollinger

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=2034055.AmVRsnPTrY@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=seth.boll@gmail.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.