You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now nixpkgs has a number modules which provide a plugin system for adding extra functionality to the service. Typical examples are:
services.printing.drivers - print drivers
hardware.sane.extraBackends - scanner drivers
services.pcscd.plugins - drivers for the smart card reader
boot.extraModulePackages - modules which should be loaded on startup
Issue description
Even though we have the plugin system, it is opaque which packages can actually be used as a plugin for the respective module. The modules are often scattered around in different folders (most notably with services.pcscd.plugins ).
Most of the time i simply grep the nixpkgs sources for keywords which may relate to the plugin i am looking for.
Steps to reproduce
Try to find all plugins for pcscd (there are at least 4 on the stable channel)
Try to find all backends for sane
Technical details
I do not know how what the best way would be to solve this issue, not all packages which can be plugins are only plugins but provide binaries or libraries as well. Maybe we could introduce a meta attribute which hints towards the package(s) or module(s) which can ingest them as plugins.
In the options search this information could be used to backtrace which extra packages are available.
The text was updated successfully, but these errors were encountered:
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Right now nixpkgs has a number modules which provide a plugin system for adding extra functionality to the service. Typical examples are:
services.printing.drivers
- print drivershardware.sane.extraBackends
- scanner driversservices.pcscd.plugins
- drivers for the smart card readerboot.extraModulePackages
- modules which should be loaded on startupIssue description
Even though we have the plugin system, it is opaque which packages can actually be used as a plugin for the respective module. The modules are often scattered around in different folders (most notably with
services.pcscd.plugins
).Most of the time i simply grep the nixpkgs sources for keywords which may relate to the plugin i am looking for.
Steps to reproduce
Technical details
I do not know how what the best way would be to solve this issue, not all packages which can be plugins are
only
plugins but provide binaries or libraries as well. Maybe we could introduce a meta attribute which hints towards the package(s) or module(s) which can ingest them as plugins.In the
options
search this information could be used to backtrace which extra packages are available.The text was updated successfully, but these errors were encountered: