4 ms·

My fantasy vision, predating go, was publisher/project/version with /src and /bin below all that (separate bins and srcs). I am open to re-balancing that tree

by jjindev 13y ago

My fantasy vision, predating go, was publisher/project/version with /src and /bin below all that (separate bins and srcs). I am open to re-balancing that tree ;-), but somewhat surprised that version wasn't in from the beginning. Perhaps there were more worms in that can that I expected. (version should be constrained to x.y.z numeric form)

grey-area 13y ago
My fantasy vision, predating go, was publisher/project/version with /src and /bin Yes in a way that feels more natural to me too - all your stuff is in one place, including src and binaries, not mixed up with other binaries/source and all under one version. The current scheme does follow unix conventions though and it's not too important. The only persuasive criticism I've seen of versioning is that it doesn't deal with dependency hell automatically, however I'm not sure it can or should, and having simple versioning would be a nice step up from simply checking out master at the time you happen to go get, which means go get is not a reliable tool for fetching dependencies if you don't freeze them somehow (hence the contortions of this developer). It's not a huge deal though, and I'm sure it'll be addressed somehow at some point and the meantime there are various possible workarounds.