Should provides go inside /stow/providers/*?

[matryer]

We have a few root directories "test", "build", etc. Should we put provides inside a subdirectory or are we OK with them being alongside non-provider dirs?

[matryer]

@Xercoy @jasonhancock @dahernan @sekchai2 @piotrrojek?

[Xercoy]

👍 - Good idea, especially important as we add more providers. The test and build dirs already do the job of grouping relevant files together, so it makes sense to follow suit.

[dahernan]

Maybe separate repositories for each provider, so if you use local + Azure, you don't have to pull AWS

[piotrrojek]

I wouldn't make seperate repos for each. Each implementation is small enough that it doesn't hurt having it in the same repo IMHO.
Yes for "providers" folder inside repo though.

[matryer]

Trouble is the gigantic dependencies for some of the packages - it means Stow ends up having every other Go package in the world as a dependency.

[piotrrojek]

Valid point.
Seperate repos then? stow-azure, stow-s3 etc.?

[matryer]

Turns out, go get for github.com/graymeta/stow will only get the root package, not all the dependencies for all providers. So we are ok to keep them in the same repo. But should we nest them inside providers?

[matryer]

I think it's simpler as it is. Closing.