Commit Graph

5 Commits

Author SHA1 Message Date
Fabian Bläse 1ea9796074 babeld: Revise version string
As the originally used version string did not include
the daemons name, it is changed to versions like:

babeld-1.9.1+fff2

Signed-off-by: Fabian Bläse <fabian@blaese.de>
2019-11-17 22:14:43 +01:00
Fabian Bläse 9fc263d093 Bump openwrt, packages and routing to v18.06.5, rebase patches
Signed-off-by: Fabian Bläse <fabian@blaese.de>
2019-11-17 22:14:43 +01:00
Adrian Schmutzler c4d6e231be babeld: Add pending patch for src_plen assignments
This introduces the pending upstream fix and a patch to change
babeld version.

This applies the naming scheme as for batman-adv:

openwrt-PKG_VERSION-PKG_REVISION

e.g. openwrt-1.9.1-2

Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Reviewed-by: Fabian Bläse <fabian@blaese.de>
2019-11-17 22:14:43 +01:00
Fabian Bläse d40761c13b Add feed patch to update babeld to 1.9.1
Signed-off-by: Fabian Bläse <fabian@blaese.de>
Acked-by: Christian Dresel <fff@chrisi01.de>
2019-09-29 21:22:33 +02:00
Adrian Schmutzler 014f66a8d7 buildscript/patches: Automatically scan directories for feeds
The buildscript knows two different types of patches, which are
applied to pulled-in repositories:

1. Feed patches
Those are applied as "GIT patches" to the relevant repos,
directly after those have been checked out.
They reside in subfolders of the build_patches folder, and
have to be selected individually and manually in the
buildscript.sh.

2. Build patches
Those are applied later in the process, just using the system
patch tool, and changing the $target directory.
All patches in the folder "build_patches/openwrt" are read
and applied automatically.

This is both inconsistent (two different types of patches in
the same dir) and annoying (feed patches have to be specified
by hand), especially for unexperienced developers.

This patch addresses this by:
- separating files into two dirs: build_patches and feed_patches
- automatically scanning feed patches and thus having similar
  experience for the user (I cannot think of a case where we
  provide a patch, but do not use it)

Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Reviewed-by: Robert Langhammer <rlanghammer@web.de>
2019-04-10 15:26:16 +02:00