Something that is still unclear to me even after reading todays post is how I would manage the various package import paths created by the import compatibility rule. The way this is currently done is through tools such as gopkg.in, will the import path be modified and rewritten by a package server in the future? If not, do I maintain separate /v2 and /v3 trees in my directory and copy/paste changes between them when I want to release security fixes as a point release? Do I maintain separate branches that have a single /v2 or /v3 tree (if so, cherry-picking changes between them will be very difficult)? Do I maintain separate repos and cherry pick or copy/paste files between them?
None of these sound especially appealing except perhapse having a server handle it for me, but this makes hosting my own packages harder. —Sam -- Sam Whited s...@samwhited.com -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
