I'm working on a new project and I've been trying to define the best way to
manage the components and the dependencies.
The structure would be something like this:
- Main_Project
|
|-- README.md
|
|-- LICENSE
|
|-- src
|-- go_project_1 //this is an individual repo which is a subtree of the
main repo
| |
| |-- stuff
| |
| |-- vendor
| |
| |-- dependencies
|
|-- go_project_2 //this is another individual repo which is a subtree of
the main repo
|
|-- stuff
|
|-- vendor
|
|-- dependencie_with_glide //this one has other dependencies
and the project uses a glide.yaml for dependency management
|
|-- dependencies
I wanted to manage my dependencies with submodules so the whole project could
be cloned with *git clone --recursive*, but I can't do that
I was thinking about forking that specific dependency and add all its
dependencies through submodules but it doesn't seem to be a very elegant
solution...
my other option would be migrating the project from submodules to glide but
although it would be more convenient in some ways, I think
that would make downloading the code a more tedious process:
*-git clone*
-*cd* the the first subtree and
*glide up*-*cd* the the second subtree and
*glide upI don't know what to do now.*
--
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.
