Separate plugins with duplicate names within one source repository

[sumpfralle]

Some plugins in the munin repository have the same name:

$ find plugins/ -name cpu.in
plugins/node.d.netbsd/cpu.in
plugins/node.d.linux/cpu.in
plugins/node.d.freebsd/cpu.in
plugins/node.d.sunos/cpu.in
plugins/node.d.aix/cpu.in

Only one of these plugins (maybe even a random one) is the final plugin to be presented in the plugin gallery.

Instead the generator should detect duplicate names and try to add a unique token based on the distinct part of the filename's path (e.g. cpu (linux) or linux/cpu).

[steveschnepp]

I don't really mind decimating the plugins by names, regardless of where there are. But we should simply point to the various implementations, while keeping the page unique.

Also, we could move towards name "unification". Meaning that if a plugin has the same name, we expect it to have the same output, or something very similar. At least visually.

Which isn't solved by the gallery, but gallery will help unification, as it offers a aggregated view

[sumpfralle]

I don't really mind decimating the plugins by names, regardless of where there are. But we should simply point to the various implementations, while keeping the page unique.

Since the main content of each plugin page is its documentation and the plugin code (both will vary inevitably), I cannot really imagine a fair/generic approach for merging these into one.

But maybe providing a list of alternatives (plugins with the same name) right at the top of each plugin page could be a good approach to solve this? This could also work nicely for plugins targeted at different versions of the service being monitored (e.g. asterisk_14 and asterisk_18). I think, this could be useful.