From: Matthew Weber <matthew.weber@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] skeleton: /etc/network/interface.d/* support
Date: Mon, 24 Oct 2016 21:22:37 -0500 [thread overview]
Message-ID: <CANQCQpamR1dU8zTt_XwX_u2MgzLW3dBvw5e3Tc=RmGfhwW3g+Q@mail.gmail.com> (raw)
In-Reply-To: <20161023141720.626b89d6@free-electrons.com>
Thomas/ Peter
On Sun, Oct 23, 2016 at 7:17 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
>
> Hello,
>
> On Sun, 23 Oct 2016 14:06:12 +0200, Peter Korsgaard wrote:
>
> > We afaik provide no explicit guarantees on the ordering of the various
> > _TARGET_FINALIZE hooks
>
> Correct.
>
> >, but it afaik will run in (package-)alphabetical
> > order, E.G. before the finalize hooks of skeleton so this doesn't work
> > :/
>
> Hum, my thinking was that it did not matter if the "source" line is
> before or after the lo definition. However, the skeleton package
> completely overwrites the file, so indeed, it doesn't work.
So leave it as is in the skeleton.mk?
--
Matthew L Weber / Pr Software Engineer
Airborne Information Systems / Security Systems and Software / Secure Platforms
MS 131-100, C Ave NE, Cedar Rapids, IA, 52498, USA
www.rockwellcollins.com
Note: Any Export License Required Information and License Restricted
Third Party Intellectual Property (TPIP) content must be encrypted and
sent to matthew.weber at corp.rockwellcollins.com.
next prev parent reply other threads:[~2016-10-25 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 15:38 [Buildroot] [PATCH v2] skeleton: /etc/network/interface.d/* support Matt Weber
2016-10-22 21:28 ` Thomas Petazzoni
2016-10-23 12:06 ` Peter Korsgaard
2016-10-23 12:17 ` Thomas Petazzoni
2016-10-25 2:22 ` Matthew Weber [this message]
2016-10-25 6:25 ` Peter Korsgaard
2016-10-25 13:14 ` Matthew Weber
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='CANQCQpamR1dU8zTt_XwX_u2MgzLW3dBvw5e3Tc=RmGfhwW3g+Q@mail.gmail.com' \
--to=matthew.weber@rockwellcollins.com \
--cc=buildroot@busybox.net \
/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.