Seebs 0eba050054 stop using pkg/plugin, start using build tags ... After a few experiments with pkg/plugin, I'm ready to concede that the people warning me it was unsuitable for production use were in fact correct. In the brave new world, the "ext" package is moved to its own module outside pilosa. This means that importing it doesn't imply any need to version-check against pilosa; we can just use versioned copies of the ext package, which can be public because it doesn't contain anything we need to care about keeping proprietary. Then we can, conditional on build tags, import modules from a neighboring repo which contains the actual implementations, and if they're imported, their init functions register them.		2019-12-20 12:21:47 -06:00
..
distinct.go	stop using pkg/plugin, start using build tags	2019-12-20 12:21:47 -06:00
dummy.go	stop using pkg/plugin, start using build tags	2019-12-20 12:21:47 -06:00