On Fri, Dec 16, 2016 at 8:15 AM, David Norton <dgnor...@gmail.com> wrote: > Or, maybe tell the go tool which package to consider "main" instead of > listing all packages. Would that work?
I didn't mean to imply that it is necessary to list every package in the plugin. The plugin would contain those packages plus all packages that they import. Given that, I think your suggestion is equivalent to building a plugin by listing a single package. Ian > On Friday, December 16, 2016 at 11:12:09 AM UTC-5, Ian Lance Taylor wrote: >> >> On Fri, Dec 16, 2016 at 8:09 AM, David Norton <dgno...@gmail.com> wrote: >> > We're experimenting with the new plugin package (in go 1.8 beta) in >> > telegraf. It would be convenient if plugin code could be in any package >> > and >> > not required to be in "package main". Is that possible? For example, if >> > we >> > wanted a package to allow both the typical static linking and building >> > as a >> > plugin (shared library). Currently, this requires having code for the >> > same >> > plugin split between different directories, one for the plugin's package >> > and >> > one for package main. >> >> One could imagine a mode in which the go tool is given a list of >> packages to put into the plugin and auto-generates a main package that >> imports those packages. >> >> Ian > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
