nixcord: add Equibop and Equicord support

[make-42]

Adds Equibop and Equicord support to the nixcord module.

---

• I certify that I have the right to submit this contribution under the MIT license
• Commit messages adhere to Stylix commit conventions
• Theming changes adhere to the Stylix style guide
• Changes have been tested locally
• Changes have been tested in testbeds
• Each commit in this PR is suitable for backport to the current stable branch

[0xda157]

1. can you add testbed(s) for this
2. the nested mkMerge/mkIfs are getting very hard to parse, it would be nice if the logic could be extracted to make it more readable (in a separate commit) (not required)

[make-42]

sure

[make-42]

For 1. though, since nixcord isn't imported by stylix I don't think I'm actually able to pull the nixcord options in to use in a testbed

[0xda157]

For 1. though, since nixcord isn't imported by stylix I don't think I'm actually able to pull the nixcord options in to use in a testbed

feel free to add nixcord as a dev input, #1994 might be a helpful example.

[make-42]

sure

[make-42]

adding nixcord as a dev input doesn't grant me access to it from a testbed for some reason

[make-42]

[make-42]

having added this to flake/dev/flake.nix

and having run
nix flake update nixcord
in that dir

[make-42]

am i missing anything?

[make-42]

i get the following error

[make-42]

oh and i also did add it to stylix/testbed/default.nix

[make-42]

i did

[0xda157]

i get the following error

the testbed needs to be called nixcord-equibop for nixcord to be imported

[make-42]

that does indeed work

[make-42]

for some reason the option is now allowed to be enabled but the testbed doesn't have the package

[make-42]

(i probably just forgot to enable nixcord)

[0xda157]

LGTM

[make-42]

tiny typo i've got left to fix

[make-42]

now it should be all good

[make-42]

screenshot from the testbed:

[make-42]

actually new error with the new flake file:

[0xda157]

seems like nixpkgs.config.allowUnfreePredicate isn't applying to the buildbot runners (which is expected). @zowoq is there any way around this so we can still build our testbeds that have unfree packages?

[zowoq]

seems like nixpkgs.config.allowUnfreePredicate isn't applying to the buildbot runners (which is expected)

Why is that expected?

If allowUnfree is set on a package buildbot should respect it.

[0xda157]

seems like nixpkgs.config.allowUnfreePredicate isn't applying to the buildbot runners (which is expected)

Why is that expected?

If allowUnfree is set on a package buildbot should respect it.

nvm I'm pretty sure it isn't expected, still an issue regardless.

[0xda157]

seems like nixpkgs.config.allowUnfreePredicate isn't applying to the buildbot runners (which is expected)

Why is that expected?
If allowUnfree is set on a package buildbot should respect it.

nvm I'm pretty sure it isn't expected, still an issue regardless.

nvm this is happening on gh actions too, it's an issue with the config. @make-42 you'll have to remove testbeds from this pr and I'll work on resolving the issue in a follow up (it requires being able to access inputs from the testbed).

[make-42]

okay, i'll revert the testbeds

[make-42]

Should be good to go

[pastadudes]

LGTM and works for me!
thank you people

[Flameopathic]

What's there looks good, and I like the abstraction (but the name is a little unclear; maybe something like writeConfigFile?). Would love to see that testbed implemented. Not sure why there are any issues with this testbed that aren't present in NixVim etc.

[0xda157]

Would love to see that testbed implemented. Not sure why there are any issues with this testbed that aren't present in NixVim etc.

because discord is unfree and nixcord uses their own package, not the one in nixpkgs.

[trueNAHO]

seems like nixpkgs.config.allowUnfreePredicate isn't applying

Is this the same problem as in #1662 (comment)?