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
The current code imports the latest version of the required packages and it's not possible to build anymore due to some changes in Iris. We need a package manager that can fix this issue for us, by locking the packages versions. That's where Glide comes in.
However, if we are to implement Glide, we have two options available:
Add a workaround to the virtual env scripts, which copies the dependencies installed from vendor/ to vendor/src
Change our current directory structure
In case we choose the latter, a proposed directory structure by @StollD can fix the issue:
Since my previously proposed directory structure makes things even worse, I suggest that we drop the virtualenv script and require that the user who wants to build sdb sets his gopath accordingly. This would result in something like:
My previously proposed structure would expect the vendor folder in src/github.com/KSP-SpaceDock/SpaceDock-Backend/vendor and not in the repository root, which can easily get problematic (especially with long filenames on windows).
Instead of the activate scripts in build, we would have two scripts, one for installing glide and one for preparing the build_sdb.go file. Sadly there is no way to make it easily go-installable, because that would also take care of the compiling for us.
The current code imports the latest version of the required packages and it's not possible to build anymore due to some changes in Iris. We need a package manager that can fix this issue for us, by locking the packages versions. That's where Glide comes in.
However, if we are to implement Glide, we have two options available:
vendor/
tovendor/src
In case we choose the latter, a proposed directory structure by @StollD can fix the issue:
The text was updated successfully, but these errors were encountered: