Giters
kardianos
/
vendor-spec
Go vendor file specification.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
90
Watchers:
13
Issues:
34
Forks:
4
kardianos/vendor-spec Issues
Spec should include a way to describe the tool used to generate the file
Closed
5 years ago
Comments count
2
Support for directories other than "vendor/"
Updated
8 years ago
Comments count
8
make revisionTime optional
Closed
9 years ago
Comments count
15
Include license in specification
Closed
9 years ago
Comments count
13
Can godep use vendor-spec?
Updated
9 years ago
Comments count
1
origin field meaning should be more nuanced.
Closed
9 years ago
Comments count
2
list tool support on front page
Updated
9 years ago
Comments count
10
Purpose
Closed
9 years ago
Comments count
2
allow/encourage placing vendor.json in vendor directory (not above it)
Closed
9 years ago
Comments count
1
example uses originPath, originURL without definition
Closed
9 years ago
Comments count
1
do not require both canonical and local
Closed
9 years ago
Comments count
4
replace "canonical", "local" with clearer names
Closed
9 years ago
Comments count
20
Update examples to use GO15VENDOREXPERIMENT
Closed
9 years ago
Comments count
5
Vendor-spec should become a go proposal
Closed
9 years ago
Comments count
5
example times are wrong
Closed
9 years ago
Reasoning behind required RevisionTime field
Closed
9 years ago
Comments count
2
only support tags, not revision pointers
Closed
9 years ago
Comments count
9
don't call it a vendor file
Closed
9 years ago
Comments count
2
spec: Schema version required
Closed
9 years ago
Comments count
6
Vendor spec from `nut`'s perspective
Closed
9 years ago
Comments count
5
reconsider using Go-style uppercase field name capitalization
Closed
9 years ago
Comments count
3
spec: non canonical fields should be required to have a `x-` prefix
Closed
9 years ago
Comments count
4
Change name of Vendor field
Closed
9 years ago
Comments count
2
spec: Local field is redundant
Closed
9 years ago
Comments count
3
consider providing an alternate history URL
Closed
9 years ago
Comments count
3
Example 1, packages tls and context is incorrect
Closed
9 years ago
Comments count
15
Should Package fields "Vendor" and "Local" both be mandatory?
Closed
9 years ago
Comments count
1
Consider requiring tools to preserve all unrecognized fields
Closed
9 years ago
Comments count
2
Consider adding Package field "ImportAs"
Closed
9 years ago
Consider removing RevisionTime
Closed
9 years ago
Comments count
1
Consider adding a 'Comment' field to the package struct?
Closed
9 years ago
Comments count
1
spec: Package.Version should be Package.Revision
Closed
9 years ago
Comments count
2
Two questions
Closed
9 years ago
Comments count
5
vendor hangs on "vendor add golang.org/x/net" and similar
Closed
9 years ago
Comments count
3