Comments (5)
zimbatm
commented on June 11, 2024
1
The only difference is when using nix flake check, it will complain if packages isn't a flat attrset of packages only. legacyPackages allows any types of values. When you use commands like nix run it will look into both, and prioritize packages over legacyPackages.
from flake-utils.
shadowrylander
commented on June 11, 2024
Sorry; just understood the error. What measures does Hydra take to handle failing packages, or where can I find them? This, for example, gets killed:
filterAttrs (n: v: all (b: b == true) [
(! elem n [ "prometheus-dmarc-exporter" ])
(tryEval v).success
((isDerivation v) && (v ? meta) && (v.meta ? broken))
]) legacyPackagesfrom flake-utils.
zimbatm
commented on June 11, 2024
Most likely this will also use a ton of memory. flattenTree probably shouldn't be used like that 😅
from flake-utils.
shadowrylander
commented on June 11, 2024
Aww... 😹 Ah, well; I guess I could just use legacyPAckages. Could you tell me the difference between it and packages, actually?
from flake-utils.
shadowrylander
commented on June 11, 2024
Ah; makes sense. Thanks for the clarification!
from flake-utils.
Related Issues (20)
- nix flake check fails with overlays because arguments are not properly named HOT 2
- Transfer to nix-community? HOT 3
- Nixos module in simple flake HOT 1
- simpleFlake exposes `overlays` output as list HOT 1
- simpleFlake to support defaultSystems HOT 2
- Outputs spec update makes `eachSystemMap` powerful HOT 2
- flake-utils.lib.mkApp is broken with nix 2.8 HOT 4
- move functions to nixpkgs HOT 2
- Use `meta.mainProgram` by default in `mkApp` HOT 4
- Request for Semantic Version Pinning HOT 1
- Request for Semantic Version Pinning HOT 1
- Should `filterPackages` check `meta.hydraPlatforms`? HOT 2
- nixops support HOT 4
- self parameter for eachSystem/eachDefaultSystem HOT 2
- single arch+os override flake HOT 15
- Potential feature-freeze or deprecation in favor of flake-parts HOT 2
- master rename to main breaks nix flake update HOT 3
- eachDefaultSystem docs are sorely missing a real example HOT 4
- This `flake.system.nix` approach... relies on a broken nix feature
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from flake-utils.