From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/2] add frr package
Date: Tue, 25 Feb 2020 17:53:20 +0200 [thread overview]
Message-ID: <20200225155322.8440-1-vadim4j@gmail.com> (raw)
FRR is free software that implements and manages various IPv4 and IPv6
routing protocols. It runs on nearly all distributions of Linux and BSD
as well as Solaris and supports all modern CPU architectures.
FRR currently supports the following protocols:
BGP
OSPFv2
OSPFv3
RIPv1
RIPv2
RIPng
IS-IS
PIM-SM/MSDP
LDP
BFD
Babel
PBR
OpenFabric
VRRP
EIGRP (alpha)
NHRP (alpha)
FRR package requires LYD_PRIV option to be enabled in
libyang package, so enabled it in separate patch if
frr is selected.
Disabled some options for frr package like:
- POSIX capabilities
- RPKi
v3:
1) Remove hook with bootsrap running, autoreconf handles everything
2) Remove _SOURCE var, it is auto-generated
3) Remove --disable-exampledir which causes install config samples
into "$(TARGET_DIR)no" folder, but remove them from $(TARGET_DIR)/etc/frr
in POST_INSTALL hook.
4) Enable LYD_PRIV option for libyang by default because there is no
size difference with or without this option.
v2:
1) fixed TAB indent on multiline var assignment
2) fixed ABC ordering
3) add missing 'depends on' from selected libs by frr
4) directly call /usr/sbin/frrinit.sh S50frr init script
w/o start-stop-daemon tool, frr cares of daemons stopping/
running.
5) Removed not-needed empty daemons *.conf files installation,
it was taken from building instructions in frr docs, but
really it is not required.
6) Use 0644 mask for conf files.
7) Enable LYD_PRIV option for libyang only if frr selected.
8) Drop patch with rtrlib package which is needed only for
RPKi support which is disabled by default.
9) Add AUTORECONF for bootstrap invocation.
10) Get rid of manual binaries target invocation. After frr.mk
cleanup it starts to work.
11) Install var/log/frr and /var/run/frr at runtime from init.
Vadim Kochan (2):
package/libyang: enable LYD_PRIV option for frr package
package/frr: new package
DEVELOPERS | 1 +
package/Config.in | 1 +
package/frr/Config.in | 25 ++++++++++++++
package/frr/S50frr | 46 +++++++++++++++++++++++++
package/frr/frr.hash | 2 ++
package/frr/frr.mk | 69 ++++++++++++++++++++++++++++++++++++++
package/libyang/libyang.mk | 3 +-
7 files changed, 146 insertions(+), 1 deletion(-)
create mode 100644 package/frr/Config.in
create mode 100644 package/frr/S50frr
create mode 100644 package/frr/frr.hash
create mode 100644 package/frr/frr.mk
--
2.17.1
next reply other threads:[~2020-02-25 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 15:53 Vadim Kochan [this message]
2020-02-25 15:53 ` [Buildroot] [PATCH v3 1/2] package/libyang: enable LYD_PRIV option for frr package Vadim Kochan
2020-08-26 21:11 ` Thomas Petazzoni
2020-02-25 15:53 ` [Buildroot] [PATCH v3 2/2] package/frr: new package Vadim Kochan
2020-08-26 21:13 ` Thomas Petazzoni
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=20200225155322.8440-1-vadim4j@gmail.com \
--to=vadim4j@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox