In reply to @blaggacao:matrix.org
If a fix cold expose or clarify this upstream "shortcoming", that would be really useful. Maybe a prominent code comment or something.

reading man nix.conf it sounds like extra-* is what we're looking for

A configuration setting usually overrides any previous value. However, you can prefix the name of the setting by extra-  to  append  to  the
       previous value. For instance,

       substituters = a b
       extra-substituters = c d

       defines the substituters setting to be a b c d. This is also available as a command line flag (e.g. --extra-substituters).

In reply to @teutat3s:pub.solar

reading man nix.conf it sounds like extra-* is what we're looking for

A configuration setting usually overrides any previous value. However, you can prefix the name of the setting by extra-  to  append  to  the
       previous value. For instance,

       substituters = a b
       extra-substituters = c d

       defines the substituters setting to be a b c d. This is also available as a command line flag (e.g. --extra-substituters).

In reply to @blaggacao:matrix.org
Gytis Ivaskevicius: is the target the editable path?

In reply to @teutat3s:pub.solar

reading man nix.conf it sounds like extra-* is what we're looking for

A configuration setting usually overrides any previous value. However, you can prefix the name of the setting by extra-  to  append  to  the
       previous value. For instance,

       substituters = a b
       extra-substituters = c d

       defines the substituters setting to be a b c d. This is also available as a command line flag (e.g. --extra-substituters).

We'd have to test this. I suspect if it's

extra-substituters = c d
extra-substituters = a

only a would be left?

~
❯ nix-cd g-firefox

/nix/store/vdsgmh16gknhy47z0y39kk5yj2m7sw94-firefox-89.0.2
❯

In reply to @blaggacao:matrix.org
Gytis Ivaskevicius: I've to win you over for divnix/bud where we could land the users within the editable directory (if it's a custom pkg). Or we could even boostrap an overlay to modfy upstream in the appropriate local place.

Like:

• "I want to modify my firefox"
• nix-j firefox
• profit!

target=$(nix eval --expr "(builtins.getFlake "flake:self").outputs.pkgs.${system}.nixpkgs.$1.outPath" --impure --raw)
base=$(nix eval --expr "(builtins.getFlake "flake:self").outPath" --impure --raw)
cd $FLAKEROOT/$(diffpath? target base)

target=$(nix eval --expr "(builtins.getFlake "flake:self").outputs.pkgs.${system}.nixpkgs.$1.outPath" --impure --raw)
base=$(nix eval --expr "(builtins.getFlake "flake:self").outPath" --impure --raw)
cd $FLAKEROOT/$(diffpath? target base)

(not sure what's the command for diffpath)

target=$(nix eval --expr "(builtins.getFlake "flake:self").outputs.pkgs.${system}.nixpkgs.$1.outPath" --impure --raw)
base=$(nix eval --expr "(builtins.getFlake "flake:self").outPath" --impure --raw)
cd $FLAKEROOT/$(diffpath? target base)

(not sure what's the command for diffpath, but you get the idea)

In reply to @gytis-ivaskevicius:matrix.org
im interested in the editing part

In reply to @blaggacao:matrix.org
in divnix/bud we have FLAKEROOT wich is guarantted to be the editable root of the system flake.

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

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