Re: [LEDE-DEV] How LEDE knows when to "reinstall" base-files (after revision change)?

On 3 November 2016 at 17:51, Rafał Miłecki wrote: > I'm trying to understand how REVISION variable and getver.sh work. There is > this > nice feature: whenever a new git commit appears, getver.sh is used to > calculate > new revision and it's used for /etc/openwrt_version.

Re: [LEDE-DEV] How LEDE knows when to "reinstall" base-files (after revision change)?

On 11/03/2016 06:44 PM, Jo-Philipp Wich wrote: I think its not actually noticing all git commits but rather most of them. The base-files package registers some explicit file depends using: PKG_FILE_DEPENDS:=$(PLATFORM_DIR)/ $(GENERIC_PLATFORM_DIR)/base-files/ which means that its stamp files

Re: [LEDE-DEV] How LEDE knows when to "reinstall" base-files (after revision change)?

Hi Rafal, I think its not actually noticing all git commits but rather most of them. The base-files package registers some explicit file depends using: PKG_FILE_DEPENDS:=$(PLATFORM_DIR)/ $(GENERIC_PLATFORM_DIR)/base-files/ which means that its stamp files are invalided whenever any file in

[LEDE-DEV] How LEDE knows when to "reinstall" base-files (after revision change)?

From: Rafał Miłecki I'm trying to understand how REVISION variable and getver.sh work. There is this nice feature: whenever a new git commit appears, getver.sh is used to calculate new revision and it's used for /etc/openwrt_version. LEDE never misses an update of git commit.