On 28/07/16 23:32, Ian Eyberg wrote:
Just some quick thoughts:
I have trouble guessing what exactly your quick thoughts mean. Can you expand on your thoughts a bit so as to make an explicit connection with the discussion?
1) We have 2 builds of Go (1.5) and (1.7) on gorump. Building either of them takes a long time to do. Then you have to run your 'tests'. Keeping these separate allows one to iterate faster and not have to wait on other packages. One of the reasons we kept the go stuff separate is because I didn't want to be bound by build/test times from outside code.
What does "separate" mean? separate between 1.5 and 1.7? separate from other packages? Either way, I don't see why you'd be bound by "outside" code that you're not going to build or use.
2) All of the interpreted languages require a hodepodge of various libraries to link against and so it's never going to be the case outside of hello world examples that you wouldn't have completely different builds for them.
Why do you specifically pick out interpreted languages? All code ever links against various libraries depending on what the code wants to accomplish.
The packages repo is a great base to work on but I'd expect a lot more different structures to evolve in the future.
Yes I'd expect evolution and development too.
