From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/frr: new package
Date: Mon, 24 Feb 2020 23:07:06 +0100 [thread overview]
Message-ID: <20200224230706.254c00d3@windsurf> (raw)
In-Reply-To: <20200224213654.GA41047@archlinux>
On Mon, 24 Feb 2020 23:36:54 +0200
vadim4j at gmail.com wrote:
> > Huh? That's not what I'm asking here. I'm just asking that you look at
> > the definition of each of those options, and if any of them has some
> > "depends on" dependency, you need to replicate them into the frr
> > package Config.in file.
> Hmmm, you mean to add here "depends on" from selected packages ?
Yes, like we do in all other Buildroot packages.
See also section "17.2.3. Choosing depends on or select" in
https://buildroot.org/downloads/manual/manual.html.
> > > > So it's the frrinit.sh script that requires bash ?
> > > Yes, this is runtime dependency.
> >
> > And using this script is important?
> Well, it runs daemons on system init to handle routing
> protocols.
OK, but is it complicated? Can it be replaced by some simpler
Buildroot-compliant init script?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-24 22:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:26 [Buildroot] [PATCH 0/3] add frr package Vadim Kochan
2020-02-24 17:26 ` [Buildroot] [PATCH 1/3] package/libyang: enable LYD_PRIV option Vadim Kochan
2020-02-24 19:52 ` Thomas Petazzoni
2020-02-24 20:36 ` vadim4j at gmail.com
2020-02-24 17:26 ` [Buildroot] [PATCH 2/3] package/rtrlib: new package Vadim Kochan
2020-02-24 19:53 ` Thomas Petazzoni
2020-02-24 21:00 ` vadim4j at gmail.com
2020-02-24 17:26 ` [Buildroot] [PATCH 3/3] package/frr: " Vadim Kochan
2020-02-24 20:06 ` Thomas Petazzoni
2020-02-24 21:14 ` vadim4j at gmail.com
2020-02-24 21:32 ` Thomas Petazzoni
2020-02-24 21:36 ` vadim4j at gmail.com
2020-02-24 22:07 ` Thomas Petazzoni [this message]
2020-02-25 1:28 ` vadim4j at gmail.com
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=20200224230706.254c00d3@windsurf \
--to=thomas.petazzoni@bootlin.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.