-
Notifications
You must be signed in to change notification settings - Fork 41
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
Flakestry releases #208
Comments
The DetSys FlakeHub site handled their own mirroring of desirable inputs without forcing the owners to add a CI step for their own benefit. Flakestry could follow a similar strategy if they want to help adoption of their tool, otherwise we'll see pleas like this one on most repos, which I don't think is necessarily a fair burden. |
Do you have an concrete reason why you need this? So while I don't see much immediate benefit, I think at some point it may be useful. By maintaining both systems that flake-parts couples with: Nix and the module system, I can actually state with some confidence that this will take a long time before it's useful. Finally I'd like to avoid GHA. Last time I checked, it seemed that auth was coupled to GHA specifically, so either
Hardcoding a forge in the registry URL layout seems like a bad idea, so I hope the latter will be implemented, even if less convenient.
This could also be implemented for |
mypy: allow adding custom paths to PYTHONPATH
It would be really cool if flake-parts would be on Flakestry.
Here is the announcement post in the NixOS forum:
https://discourse.nixos.org/t/announcing-flakestry-dev-new-registry-for-flakes/34583
Publishing rolling releases is currently blocked by flakestry/flakestry.dev#35. However it looks like it'll be merged soon.
The text was updated successfully, but these errors were encountered: