Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

Update README.md #13

Closed
wants to merge 1 commit into from
Closed

Update README.md #13

wants to merge 1 commit into from

Conversation

smallfish
Copy link

url repeat

url repeat
@AlekSi
Copy link
Owner

AlekSi commented Dec 11, 2012

Nope, it's not a typo. nut package is a library (package nut), nut/nut is a tool/command (package main).

@AlekSi AlekSi closed this Dec 11, 2012
@ghost ghost assigned AlekSi Jan 31, 2013
@kavu
Copy link

kavu commented Mar 18, 2013

Are you sure? Well, I bet you're sure, but I can't use nut properly if i go get -u github.com/AlekSi/nut, and it works like a charm if I go get the nut/nut sub-project.

@AlekSi
Copy link
Owner

AlekSi commented Mar 18, 2013

@kavu You should type as written in README: go get -u github.com/AlekSi/nut/....

@kavu
Copy link

kavu commented Mar 19, 2013

@AlekSi Oh! 😧 Another amazing feature from Go toolchain. I definitely need to dive deeper into go get sources now. But the question is - why does go get -u github.com/AlekSi/nut/nut still works?..

@AlekSi
Copy link
Owner

AlekSi commented Mar 19, 2013

go get -u github.com/AlekSi/nut/... clones repository and installs nut and every subpackage in nut/ recursively. Dependencies are go get -u.
go get -u github.com/AlekSi/nut/nut clones repository and installs package nut/nut. Dependencies are go get -u. nut/nut depends on github.com/AlekSi/nut so it's also installed.
Docs: http://golang.org/cmd/go/#hdr-Description_of_package_lists

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants