Hi, So let's say there is a project, living under path github.com/local/project. Project is neatly divided into a bunch of packages and uses recommended absolute paths:
package main import ( "github.com/external/dep1" "github.com/local/project/config" "github.com/local/project/backend" "github.com/local/project/frontend" ) and packages inside of it also use that: package backend import ( "github.com/external/dep3" "github.com/external/dep4" "github.com/local/project/config" "github.com/local/project/backend/nosql" "github.com/local/project/backend/sql" "github.com/local/project/backend/dummy" ) package frontend import ( "github.com/external/dep5" "github.com/external/dep6" "github.com/local/project/config" "github.com/local/project/backend" "github.com/local/project/frontend/html" "github.com/local/project/frontend/pdf" ) ...how does one contribute to it ? If I just go and fork it and do a bunch of changes across packages then I can't test it because everything will be under "github.com/me/project" so deps will come from the "wrong" place. If I go and find-replace everything now I can work in peace but any diff or pull request from it wont make any sense as now it will contain wrong paths If I use relative packages then things like `go test` complain about local imports and wont run. Surely there is a better method than "just glue it with some symlinks" ? Cheers, Mariusz -- 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.
