|
Mike Gehard |
at Jul 24, 2013 at 11:48 am
|
⇧ |
| |
Thanks for the heads up Jan.
I'm relatively new to Go so wasn't sure how to not have the change the
GOPATH. If you have some time, I'd love to hear how I may be able to
organize my code in general so people didn't have to change their GOPATH.
In the meantime, I'll do some work to see how I may be able to get rid of
that requirement.
Thanks,
Mike
On Wednesday, July 24, 2013 2:27:11 AM UTC-6, Jan Mercl wrote:On Tue, Jul 23, 2013 at 11:20 PM, Mike Gehard wrote:
Thanks for the heads up Keith. Agreed that the import path is a bit on the
long side. I'll reorganize it soon and push a new version.
The README talks about GOPATH dances for running examples and for
development. That is, hmm, strange. In both cases it's not necessary
and IMO should be avoided whenever possible. Some people did not touch
their GOPATHs for years and may prefer staying like that.
-j
--
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+unsubscribe@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.