<dhewg>
jow: ucode -p '31764740/100.0', it cuts off the .4?
<Habbie>
jow, stintel said to ask you - if you happen to be familiar with dnsdist, it currently uses Lua, mostly as a configuration specification language
<Habbie>
jow, do you have any idea if ucode would fit that niche for it?
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
torv has quit [Remote host closed the connection]
Larhzu has quit [Quit: leaving]
tlj_ has quit [Remote host closed the connection]
tlj_ has joined #openwrt-devel
Larhzu has joined #openwrt-devel
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
MaxSoniX has quit [Remote host closed the connection]
MaxSoniX has joined #openwrt-devel
_lore_ has quit [Remote host closed the connection]
EyitopeION has joined #openwrt-devel
_lore_ has joined #openwrt-devel
robimarko has quit [Remote host closed the connection]
robimarko has joined #openwrt-devel
<EyitopeION>
[1] Regards to you all building OpenWRT. I need the timestamp of a particular file to be in the future in the final image. How do I do this without overriding $(TOPDIR)/version.date? If also gets overwritten if I keep the file in in $(TOPDIR}/files/<path_to_my_file> and set it there, or if it's in my $(PKG_BUILD_DIR)
<EyitopeION>
[2] I have seen the script in $(TOPDIR)/scripts/ that looks for the time to use. I have the option of setting $(TOPDIR)/version.date to a time in the future but that isn't what I need. Just this one particular file in the image needs to be in the future. I should be able to do this without hacks, I believe. OpenWRT-21.02.5 is what I'm using.
<EyitopeION>
[3] Thank you.
<dwfreed>
why does the file need to be in the future
<EyitopeION>
@dwfreed: I am careful to not go off topic, which is how to set a particular file's timestamp to the future in the final image. To your question, a process will use that file's timestamp to decide whether to download a newer version from cloud or not, or if the file doesn't exist in the first place. For a particular client (single use-case), that won't be necessary; hence, the future timestamp.
<dwfreed>
just use a uci-defaults script to change the timestamp of that file
<karlp>
if you don't have SOURCE_DATE_EPOCH set, it should just work? the last line of prepare_rootfs in include/rootfs.mk is resetting the timestamps?
dangole has joined #openwrt-devel
danitool has joined #openwrt-devel
Borromini has quit [Ping timeout: 480 seconds]
torv has joined #openwrt-devel
borek has joined #openwrt-devel
paper_ has quit [Quit: connection reset by purr]
Borromini has joined #openwrt-devel
paper_ has joined #openwrt-devel
Ansuel has joined #openwrt-devel
Ansuel has quit []
EyitopeION has quit [Remote host closed the connection]
borek has quit [Read error: Connection reset by peer]
EyitopeION has joined #openwrt-devel
EyitopeION has quit [Remote host closed the connection]
bluew has quit [Ping timeout: 480 seconds]
jlsalvador has quit [Quit: jlsalvador]
jlsalvador has joined #openwrt-devel
hanetzer has quit [Ping timeout: 480 seconds]
Tapper has joined #openwrt-devel
<jow>
dhewg: will check
<jow>
Habbie: I guess so
<dhewg>
oh sry, just missed that, CCed you again about it on a PR
Borromini has quit [Remote host closed the connection]
Borromini has joined #openwrt-devel
Borromini has quit []
csrf has joined #openwrt-devel
<ysc3839[m]>
aparcar @aparcar:matrix.org: There's also lots of legacy caches in github actions. It looks like it would create a cache for every pr. https://github.com/openwrt/openwrt/actions/caches
torv has quit [Remote host closed the connection]
torv has joined #openwrt-devel
Testing has joined #openwrt-devel
Testing has left #openwrt-devel [#openwrt-devel]
zer0def has quit [Remote host closed the connection]