-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] 改进更新配置方式 #703
Comments
之前应该还要解决lilac.py只load一次的问题。。。 |
@petronny 啊,那个是什么问题来着? |
就是现在检测依赖会读一次lilac.py 然后 archlinuxcn/lilac#48 尝试设置time_limit时也会读一次lilac.py 现在这个upstream检测估计也会。。。 |
读多次会有什么问题呢? |
除了做了重复劳动就没了吧。。。 |
那就不管它好了……你有兴趣可以尝试着把加载之后的模块缓存起来。 |
我试试 |
Ref: https://aur.archlinux.org/cgit/aur.git/commit/?h=python-git&id=7128266f2b9df6336bf6db5bc1ff1e1b5a713729 I don't think the it changes anything in clean chroots. Just keep consistent. And I hope #703 will be implemented soon :)
@farseerfc 你可以开始改 pre-commit 啦。 |
改好啦,現在 pre-commit 支持 update_on 寫在 lilac.py 裏或者出現在 nvchecker.ini ,也順便合併了之前整個放進子目錄 archlinuxcn 的那個 patch 。 |
另见 #883 。我打算把 update_on 完全迁移到 lilac.yaml 里去。 |
@farseerfc 该你的 pre-commit 更新啦~ |
pre-commit 移除了關於 nvchecker.ini 的檢查 b424854 |
问题类型 / Type of issues
像 @petronny 在 d9d0056#commitcomment-28473281 说的,把更新信息写在 lilac.py 里,比如:
这样,一个包的更新可以被多个来源的更新所触发。比如 Python 的库不仅跟踪 PyPI,而且在官方 python 包进行版本升级时也可以得到更新。
依赖:
使无效:
The text was updated successfully, but these errors were encountered: