mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] How to override default file selected by another package
Date: Wed, 7 May 2014 11:19:33 +0200	[thread overview]
Message-ID: <CABDcavZJxixjsb93NUMP74zdVTL00Xks5kHu6OafG7LRUDSaBw@mail.gmail.com> (raw)

Hello all,

Is it possible for a ptxdist package to override a file in the target rootfs, if
this file is actually "selected" by a different package?

Let me try to clarify this with an example:

Let's assume I have selected the busybox init method, and checked the
option to install /etc/init.d/networking.

This selects INITMETHOD_BBINIT_ETC_INITD_NETWORKING, which
installs a default /etc/init.d/networking script to the target's rootfs.

So far so good, this is standard behaviour.

Now I want to define a new custom ptxdist package. When this package is
selected, it should be able to override the default networking script and use
a custom version (but if the package is not selected, the default script
should be used instead -- so I cannot just put a custom version of the
script in my BSP's projectroot dir).

The problem is that if I just use install_copy in the targetinstall stage of
my new package, then the actual script that is installed to the target rootfs
will depend on the order used by ptxdist to walk through the selected
packages (the last one will win). Is this order defined?

Or am I overlooking something here?

Is it possible to do what I want to do?

Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2014-05-07  9:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CABDcavZJxixjsb93NUMP74zdVTL00Xks5kHu6OafG7LRUDSaBw@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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