Rongrong

> Also looking for ubuntu and CentOS packages that installs to `/usr/local/` instead to avoid conflict. > A package maintainer would probably change the binary name to `eternal` or `eternalterminal`....

#420 #453

#420 #453 @dingqianwen Much appreciated if you could open a PR to add a dark variant.

@mytting I've already checked that issue before but I believe that this issue differs from that: 1. Multi-node builder vs. single-node builder 2. Only the build cache from the latest-built...

I've figured out a workflow to reproduce this issue easily. Please check https://github.com/Rongronggg9/RSSHub/tree/reproduce-buildkit-cache-issue Run attempt 1: https://github.com/Rongronggg9/RSSHub/actions/runs/2248798559/attempts/1 | cache type | builder cache | exported cache [^1] | build time...

@mytting > Inline cache embeds cache metadata into the image config. The layers in the image will be left untouched compared to the image with no cache information. For more...

建议写在下方为好，本机测试 `UpdateApp` 也无法成功创建该文件，因此当前写法当且仅当用户手动删除容器 (`$WINEPREFIX`) 才会写 `PACKAGE_VERSION`。若从不删除容器，该 workaround 永远不生效，且也不能起到原有的容器版本管理的作用 (一旦发生版本升级，由于仅执行 `UpdateApp` 分支，将丢失 `PACKAGE_VERSION` 文件)。 ```sh RunApp() { progpid=$(ps -ef | grep "zenity --progress --title=${BOTTLENAME}" | grep -v grep) debug_log "run ${BOTTLENAME}...

https://github.com/gitalk/gitalk/issues/503

Since gitalk seems no longer frequently maintained for long, should next-theme distribute its own downstream gitalk CSS to at least make it readable?

> We do not plan to add dedicated option values to our API that could produce a different image based on the image type, as that would certainly over-complicate things...