Release 1.2.0 #46
Release 1.2.0 #46
Conversation
a module. imports = [ ${myChannelModulesPathk}/installer/...
Signed-off-by: David Arnold <dar@xoe.solutions>
use pkgs to collect overlays from each channel, since user only passes overlaysBuilder for each channel. Also filter out any overlays defined in inputs
This is intended to be self.overlays which allows a cleaner api to pass what overlays should be collected and used to create packages export
specifically packagesFromOverlaysBuilderConstructor and overlaysFromChannelsExporter
General exporter and builderConstructor improvements
add name and input to each channel
pass channel info to hosts as channel specialArg
sometimes the inputs argument might contain "self", so drop that if it does. This is just for safety, it usually won't contain self
with the __dontExport property
Option to not export overlay
this allows systemFlake to be called multiple times without having to pass `channels` each time. As long as it just uses self.pkgs, nixpkgs will only get evaluated once and all systemFlake calls use the same channels set
This doesn't hurt in any way, but prevents export for those who use overlaysFromChannelsExporter
always use self.pkgs instead of channels
set __dontExport to srcs overlay
includes filterPackages improvements
* Add tests/derivation-outputs * Remove cases covered by tests * Add channel patching test cases * Remove patching code leftovers as part of the example * Remove Summer CI * Add tests/overlays-flow * Fix devshell root path * Fix overlays tests * Cleanup tests * Work on hosts config test * Add rm-locks command * Add validation for host options inheritance * Evaluate builder * Add examples/minimal-multichannel * Add examples/home-manager+nur+neovim * Add examples/exporters * Remove examples/fully-featured * Remove devshell.toml * Moving files around * Fix rm-locks command and add exporters build * Improve devshell
|
@blaggacao @Pacman99 Can you guys take a look at this, I'm not sure how it works https://github.com/gytis-ivaskevicius/flake-utils-plus/blob/staging/examples/exporters/flake.nix#L36-L37 Also please go over the file structure and see if it looks good. I am still not quite happy with names, but they are acceptable I guess :D |
I'm pretty sure with 1a74204 fromOverlays should work fine. Your using it exactly right, it just needs
The file structure looks great and the flake.nix is very nice to read. Looking over staging, I don't have any complaints. |
|
Alright then, it seems that it actually works. Not sure why it did not before? 🤔 Not reproducible 👀 Also, I just realized, I should have named the folder |
I like src, its a bit more common for code repositories. But I don't care either way. |
sub-systems are not great for flakes ecosystems and this prevents exporting overriden sub-systems from nixpkgs
Co-authored-by: Mihai Fufezan <36706276+fufexan@users.noreply.github.com>
Co-authored-by: Mihai Fufezan <36706276+fufexan@users.noreply.github.com>
blaggacao
force-pushed
the
staging
branch
4 times, most recently
from
5785dfe
to
ec051ca
Compare
|
@blaggacao dude, what the hell? Who force pushes to staging and why and what are these edge cases. Please provide proper explanations |
gytis-ivaskevicius
force-pushed
the
staging
branch
from
ec051ca
to
daab9cb
Compare
|
Reverted back to daab9cb due to lack of explanation of everything |
|
@gytis-ivaskevicius To be fair: lack of "public" explanation (other than the commit comment would be more precise 😉 I'm in a bit of a hurry, but of course that is no excuse, sry. 😇 |
|
I wrote that comment before our call |
|
Flake-utils-plus 1.2.0 Branching change: Improvements:
Deprecations:
Implemented multiple exporters: (Please see examples on the project page!)
|
No description provided.