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
Please re-add module.nix #8
Comments
I'd also like to see this return; alternatively, I'd be happy to use |
If anyone wants to use { config, pkgs, lib, ... }:
let
# <dwarffs> / <dwarffs/flake.nix> also an option if you add it to NIX_PATH
dwarffs =
{ __toString = _: ./path/to/dwarffs; } //
(import ./path/to/dwarffs/flake.nix).outputs {
self = dwarffs;
nixpkgs = pkgs;
};
in
{
imports = [
# ...
dwarffs.nixosModules.dwarffs
];
# ...
} |
Either that, or the Readme should be updated accordingly. At the moment it literally reads
which obviously does not work. PS: necrobumping every year :-). How many years will this stand ? |
I would really like to use DwarfFS so that I can turn off global debug packages for my system -- not having symbols at debug time is pretty much the only reason to enable it!
However, 2f984ab inlined the
module.nix
file into the new flake description. I understand the desire to use self-contained tools likedwarffs
for experimenting with Flakes, but I'm not running the Flake branch, and dwarffs is useful without it!I'd like to propose re-adding the old
module.nix
file so DwarfFS can be used by non-flake users without writing their own. I do not know if code reuse is possible, but I don't think it's worth it for such a conceptually simple expression.Alternatively, packaging
dwarffs
upstream inside Nixpkgs would also be great IMO, but I understand if you don't want to do that since it'll directly conflict with the flake experiment...The text was updated successfully, but these errors were encountered: