In reply to @gytis-ivaskevicius:matrix.org
yeah, but werent you talking about editing any package? (like firefox)

In reply to @blaggacao:matrix.org
I guess I found the cause for my infinite recursion loop: access to self.inputs seems not always to be cool.

After refactoring digga to comply with the recent upstream fup refactoring done by fufexan, users might start to see things like:

trace: warning: You are accessing a deprecated item of the digga lib.
Please update timely, it will be remove soon.

trace: warning: Deprecated Attribute Set: lib.importers.

Please use import* functions instead:
  lib.importers.overlays    -> lib.importOverlays
  lib.importers.modules     -> lib.importModules
  lib.importers.hosts       -> lib.importHosts
  lib.importers.rakeLeaves  -> lib.rakeLeaves
  lib.importers.flattenTree -> lib.flattenTree

After refactoring digga to comply with the recent upstream fup refactoring done by fufexan, users might start to see things like:

trace: warning: You are accessing a deprecated item of the digga lib.
Please update timely, it will be remove soon.

trace: warning: Deprecated Attribute Set: lib.importers.

Please use import* functions instead:
  lib.importers.overlays    -> lib.importOverlays
  lib.importers.modules     -> lib.importModules
  lib.importers.hosts       -> lib.importHosts
  lib.importers.rakeLeaves  -> lib.rakeLeaves
  lib.importers.flattenTree -> lib.flattenTree

This stuff will probably be removed once develop is merged back into master.

The full deprecation list is here: https://github.com/divnix/digga/blob/develop/deprecated.nix

In reply to @blaggacao:matrix.org
Gytis Ivaskevicius: as a shared module and overlay api between fup and digga, could we settle on composition at the user level via fup.nixosModules.<name> & fup.overlays.<name>?

In reply to @blaggacao:matrix.org
fufexan: would you mind also looking over digga's develop branch with the critical eye that inspired https://github.com/gytis-ivaskevicius/flake-utils-plus/pull/84 ?

how does the lib.exportOverlays work in practice? I'm trying to understand what would get output as "nixpkgs/winestreamproxy" coming from this overlay

{ inputs }:
final: prev: {
  osu-stable = prev.callPackage ./osu-stable {
    wine = final.wine-tkg;
    winetricks = prev.winetricks.override { wine = final.wine-tkg; };
    inherit (final) winestreamproxy;
  };

  winestreamproxy = prev.callPackage ./winestreamproxy { wine = final.wine-tkg; };

  wine-tkg = prev.callPackage ./wine-tkg {
    wine =
      if prev.system == "x86_64-linux"
      then final.wineWowPackages.unstable
      else final.wineUnstable;
    inherit (inputs) tkgPatches oglfPatches;
  };
}