[almighty] Monorepo

[Aslak Knutsen]

https://blog.gopheracademy.com/advent-2015/go-in-a-monorepo/

The go import statement refers to a PATH in a repo somewhere. PATH !=
package.

e.g. "github.com/almighty/almighty-core/resource"

On Tue, Oct 25, 2016 at 9:35 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 25 Oct 2016, at 6:31, Suraj Deshmukh wrote:
>
> With respect to our discussion above found a lightening talk(~5min)
>> about "Monolithic repositories vs. Many repositories" [1].
>>
>> Desc:
>>
>> Deciding to use a monolithic repository or many repositories for your
>> next project is not easy. Why not using both strategies? That’s
>> possible with split.sh, an open source tool that automates the
>> splitting of a monolithic Git repository into many standalone
>> repositories.
>>
>> [1] http://www.thedotpost.com/2016/05/fabien-potencier-monolithi
>> c-repositories-vs-many-repositories
>>
>
> Interesting approach.
>
> One area of monorepos I haven't figured out is how it works wit Go's
> dependency mechanism that checks out git repos - how would one use monorepo
> for many go libraries ?
>
> /max
> http://about.me/maxandersen
>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161025/f5cbbe23/attachment.htm>