staging/blocktrron/scripts/feeds, branch master

scripts: feeds: Don’t hardcode IS_TTY

2025-11-12T11:05:53Z

When building in environments that set IS_TTY, the feeds script does not honor it and passes a hardcoded value to scan.mk, causing unwanted control characters to appear in stdout. This commit addresses the issue by checking IS_TTY and MAKE_TERMOUT variables and uses their values if defined. Closes #8039 Signed-off-by: Ernestas Kulik Link: https://github.com/openwrt/openwrt/pull/20743 Signed-off-by: Christian Marangi

scripts/feeds: implement support for --root option

2025-10-13T09:47:07Z

Some feeds might need to set the source for their packages in a different directory than the cloned one. For example a feed "test" might be an entire repository and the relevant packages that wants to be included are in the directory "foo". In such scenario the source info in the package will result in something like "feeds/test/foo/network/dnsmasq" instead of an expected entry like "feeds/test/network/dnsmasq". To give a more real-world example, this problem is currently present with OpenWrt SDK where the SDK clone the entire OpenWrt core repository as "base" feeds but the package are present in the "package" directory. This cause every package to have the source entry set to "feeds/base/package/..." conflicting with what a non-SDK build do with setting the source entry to "feeds/base/..." To solve this, actually enable support for "flags" in the feeds script and implement a new option "--root" to set the root directory for the defined feed to an inner directory. The "flags" in the feed script are no more than argument option that can be defined right after the "src-" type in the feed.conf file. This feature was partially implemented but never actually used for anything keeping it dormant with all the core piece there (the pattern regex always accounted for these extra option but they were never passed to the relevant functions) An example of the "--root" flag is the following: src-git --root=package base https://git.openwrt.org/openwrt/openwrt.git;main With "--root" defined, the script will append "_root" to the feed name clone directory and will create a symbolic link named with the feed name and pointing to the feed name clone directory + the value in root. From the previous example: feed name: base -> clone directory: base_root symbolic link: base -> base_root/package The script internally reference the "_root" directory for every update operation and OpenWrt build system transparently use the feed name directory to reference feed packages producing consistent source info entry. Link: https://github.com/openwrt/openwrt/pull/20396 Signed-off-by: Christian Marangi

scripts/feeds: shallow clone submodules

2025-03-04T11:00:19Z

When a feed has submodules, all its submodules are fully cloned whereas the feed itself is shallowed. Let's be consistent and perform shallow clones as well for the submodules. Signed-off-by: Cedric CHEDALEUX Link: https://github.com/openwrt/openwrt/pull/18003 Signed-off-by: Robert Marko

scripts/feeds: shallow clone for specific commit update

2025-03-04T11:00:19Z

When a feed is referenced with a specific commit (i.e. ^), a full clone was performed and a branch was created from the sha1 and named with the sha1. Other git clones operations are shallowed. As Git does not support clone at a specific commit, let's first perform a shallow clone to latest commit, then fetch the relevant commit and finally checkout it (no more 'pseudo' branch). It saves bandwith and significantly speeds up the feed update process. Signed-off-by: Cedric CHEDALEUX Link: https://github.com/openwrt/openwrt/pull/18003 Signed-off-by: Robert Marko

scripts/feeds: force kernel package scan after a target installation

2024-10-10T19:51:43Z

When a target is installed from a feed, the linux kernel package is scanned before the installation of this target. If some kernel module packages are defined in this feeds at the target level, there were not parsed during the scan of linux kernel package, as the target didn't exist yet. So these kernel module packages don't exist. Once the target is installed, clean the linux kernel packageinfo to force the scan of the linux kernel package next time this script (or the make command) is called. Signed-off-by: Thomas Richard Link: https://patchwork.ozlabs.org/project/openwrt/patch/mailman.117548.1727195440.1280.openwrt-devel@lists.openwrt.org/ Signed-off-by: Hauke Mehrtens

scripts/feeds: Support feed update with git pull --rebase --autostash

2024-09-08T16:54:42Z

Add feed update option '-s' that performs 'git pull --rebase --autostash': * possible local uncommited changes are autostashed before pull, * local commits are then rebased on top of the new commits pulled from origin and * finally git does 'stash pop'. This enables feed update while there are local development commits and possibly also local uncommited changes. Signed-off-by: Hannu Nyman Link: https://github.com/openwrt/openwrt/pull/15377 Signed-off-by: Robert Marko

scripts/feeds: Support feed update with git pull --rebase

2024-09-08T16:54:41Z

Add feed update option '-r' to perform "git pull --rebase" so that possible local commits are rebased on top of the new commits pulled from origin. That enables git pull while there are local development commits. Signed-off-by: Hannu Nyman Link: https://github.com/openwrt/openwrt/pull/15377 Signed-off-by: Robert Marko

build: add APK package build capabilities

2024-05-17T20:21:26Z

A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren

build: use long hashes when generating feed.buildinfo

2023-11-02T11:40:44Z

Short hashes are not guaranteed to be unambiguous forever and could collide if the repo grows over time. Git also estimates how many characters are roughly required to prevent such a collision and slowly increases the amount of characters beginning from 6, OpenWrt is already at 8. Lets use the full hash the have a predictable length and keep hashes unambiguous forever. Signed-off-by: Sandro Jäckel

feeds: use git-src-full to allow Git versioning

2022-02-14T23:24:24Z

Both $(AUTORELEASE) and $(PKG_SRC_VERSION) (from luci.git) use the Git log to determine releases and package timestamps. Feeds are shallow cloned by default, resulting in an incomplete Git log and therefore different local package versions than offered upstream. This commits sets the default feeds to use `src-git-full` to solve that. Add fixes from "2b1d92f: scripts/feeds: silence git warning by selecting pull style" to `src-git-full` Signed-off-by: Paul Spooren