Splitting GF into separate repositories

[johnjcamilleri]

There is an ongoing discussion about this issue on the gf-dev mailing list.

[fredefox]

I think this is a great idea. Particularly I'm interested in splitting pgf the Haskell bindings into a seperate repo. I imagine I'd just make a seperate repo for that and add it as a git submodule in the same location here. The build instructions will change slightly, however, let me know if this is something you are interested in.

[krangelov]

I am very much against splitting the runtimes from the compiler. Changes in the compiler are almost always linked to changes in the runtime and vice versa. Having them in different repositories is sure receipe for getting inconsitencies. It will also mean that for every change, instead of one patch I will have to make two.

…

On 4 July 2018 at 10:23, Frederik Hanghøj Iversen ***@***.***> wrote: I think this is a great idea. Particularly I'm interested in splitting pgf the Haskell bindings into a seperate repo. I imagine I'd just make a seperate repo for that and add it as a git submodule in the same location here. The build instructions will change slightly, however, let me know if this is something you are interested in. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#47 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATBZZNHsjRVNXmv_pTLjFDtjyd1Cm8O5ks5uDHuWgaJpZM4UCgZP> .

[johnjcamilleri]

I agree with Krasimir here. Things which are closely coupled should remain in the same repository.