From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Alex Kiernan <alex.kiernan@gmail.com>
Cc: OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Alex Kiernan <alexk@zuma.ai>
Subject: Re: [oe] [meta-networking][PATCH v2] ifupdown-ng: Add recipe
Date: Wed, 5 Jan 2022 09:14:53 -0300 [thread overview]
Message-ID: <CAP9ODKr_xau_sZfRjVFeA_1F6NZP2-t+SGfga_9-Hin=J3Rejg@mail.gmail.com> (raw)
In-Reply-To: <20220103163754.32439-1-alexk@zuma.ai>
Em seg., 3 de jan. de 2022 às 13:37, Alex Kiernan
<alex.kiernan@gmail.com> escreveu:
>
> ifupdown-ng is a network device manager that is largely compatible with
> Debian ifupdown, BusyBox ifupdown and Cumulus Networks' ifupdown2.
>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> Signed-off-by: Alex Kiernan <alexk@zuma.ai>
> ---
> Changes in v2:
> - drop merged upstream SBINDIR patch
>
> .../ifupdown-ng/ifupdown-ng_0.11.3.bb | 45 +++++++++++++++++++
> 1 file changed, 45 insertions(+)
> create mode 100644 meta-networking/recipes-support/ifupdown-ng/ifupdown-ng_0.11.3.bb
>
> diff --git a/meta-networking/recipes-support/ifupdown-ng/ifupdown-ng_0.11.3.bb b/meta-networking/recipes-support/ifupdown-ng/ifupdown-ng_0.11.3.bb
> new file mode 100644
...
> +do_compile () {
> + oe_runmake
> +}
> +
> +do_install () {
> + oe_runmake 'DESTDIR=${D}' install
> +}
The do_compile and do_install could be dropped as this is the default.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
prev parent reply other threads:[~2022-01-05 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 16:37 [meta-networking][PATCH v2] ifupdown-ng: Add recipe Alex Kiernan
2022-01-04 10:28 ` [oe] " Ross Burton
2022-01-05 12:16 ` Otavio Salvador
2022-01-05 12:51 ` Alex Kiernan
2022-01-05 16:36 ` Ross Burton
2022-01-05 16:37 ` Khem Raj
2022-01-05 19:06 ` Khem Raj
2022-01-05 20:31 ` Alex Kiernan
2022-01-05 12:14 ` Otavio Salvador [this message]
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='CAP9ODKr_xau_sZfRjVFeA_1F6NZP2-t+SGfga_9-Hin=J3Rejg@mail.gmail.com' \
--to=otavio.salvador@ossystems.com.br \
--cc=alex.kiernan@gmail.com \
--cc=alexk@zuma.ai \
--cc=openembedded-devel@lists.openembedded.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.