Code change:
<ins> { lib , stdenv , fetchFromGitHub , nix-update-script , meson , ninja , pkg-config , python3 , vala , gtk3 , libgee , pantheon }: stdenv.mkDerivation rec { pname = "pantheon-tweaks"; version = "1.0.1"; src = fetchFromGitHub { owner = "pantheon-tweaks"; repo = pname; rev = version; sha256 = "sha256-tAfDxX/RD7pO5PN/LaZ92Cj/iZtBI/EHb0+pORfYnPM="; }; patches = [ ./fix-paths.patch ]; nativeBuildInputs = [ meson ninja pkg-config python3 vala ]; buildInputs = [ gtk3 libgee pantheon.granite pantheon.switchboard ]; postPatch = '' chmod +x meson/post_install.py patchShebangs meson/post_install.py ''; passthru = { updateScript = nix-update-script { attrPath = pname; }; }; meta = with lib; { description = "Unofficial system settings panel for Pantheon"; longDescription = '' Unofficial system settings panel for Pantheon that lets you easily and safely customise your desktop's appearance. Use programs.pantheon-tweaks.enable to add this to your switchboard. ''; homepage = "https://github.com/pantheon-tweaks/pantheon-tweaks"; license = licenses.gpl3Plus; platforms = platforms.linux; maintainers = teams.pantheon.members; }; } </ins>

Related discussion:
text: yes, that is a concern, but we can make that clear in the description do you think it is acceptable to enable a third-party component (e.g. pantheon-tweaks) with an option like if we clarify that it is third-party in the description, which is for example displayed at the or in the documentation?
I would not recommend packaging this tweaks app. It regularly breaks since it references gsettings that aren't considered API. That's just my personal opinion though I'm not familiar with NixOS options or what that means so I can't really offer an opinion there
thanks for your opinion! the program exists and people want to use it and we at nixos want to empower users to do what they want, even if the choices could be considered bad, like installing proprietary software. that's why it's considered for advanced users. you are responsible for the choices you make and you can end up with a broken system, but it's easy to roll back to a working state. experimenting is encouraged So i think it's fine for us to offer the package, but we can clarify that "it's not recommended by elementary because it regularly breaks". I'm not familiar with NixOS options or what that means so I can't really offer an opinion there i try to explain quickly: on nixos the whole system is configured by one (or multiple) config. file. as a consequence is read-only if you want to use pantheon, you add this line to the config: that sets up pantheon with default settings. there are options to change those default, like to remove default apps you don't need... so the question here is, all current options with in the name relate to official pantheon software, but would relate to third party software, which is not visible from the name. so it might not be 100% clear all the time so my suggestion is to clarify it at least in the description of the option that it is third-party and not recommended the concern is that it could devaluate you branding like the name "pantheon"
ah okay yeah. If possible then it would great if that was not namespaced with actual parts of pantheon and instead namespaced the way you would hand extensions or apps if there's no special convention for extensions. Thanks!
i suggest then