> On Dec 16, 2016, at 11:20 AM, Doug Goldstein <car...@cardoe.com> wrote: > > On 12/15/16 5:20 PM, Ronald Rojas wrote: >> Create a basic Makefile to build and install libxenlight Golang >> bindings. Also add a template. >> >> --- >> >> Eventually this patch will contain the actual bindings package; for >> now it just includes a stub package. >> > > So I'm curious why the interest to include Golang bindings in the tree. > Most people are going to expect a Go package to behave like any other go > package and be able to grab it with "go get". But by including this in > the tree I believe that method will not work.
My plan was to name the package such that we could have an automatically-mirrored git repo in the expected place; i.e., git://xenproject.org/xenlight The “fetch the tree automatically based on the package name” distribution mechanism might be a decent fit for web-based technologies, but I think it’s a terrible fit for mature software projects like Xen; and I expect that there will be a shift in the next few years as people (re-)discover this. I want to make it work, but I think that should be secondary to actually installing the library as a part of installing a Xen package / “make install”. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel