-
Notifications
You must be signed in to change notification settings - Fork 1k
Q: Migrate / upgrade project from manifest.json / lock.json to Gopkg.toml / Gopkg.lock? #1242
Comments
hi! sorry you're running into this. no, there's really no automated path - this is why we warned pretty stridently against even committing these files until after we stabilized them. (now that we have, we guarantee backwards compatibility for however, when the format changed, very little of the semantics changed. so, you might be able to get a leg up by simply using a JSON to TOML converter (like this one, i guess?) to translate each of the files, then performing the necessary changes to the TOML result as described in #644. |
ACK. Many thanks for your reply & confirmation @sdboyer! |
The converter mentioned above failed on my
P.S.: I'm still interested in a better way to solve this problem, so please comment if you know one. |
Disclaimer: apologies in advance if I missed some doc/issue/PR answering this question already. The few searches I ran unfortunately did not yield anything.
Question:
If I have a project using the "old" format (pre #342) to define dependencies and constraints on them, i.e.:
manifest.json
lock.json
is there a way to have
dep
migrate or upgrade the project from these to the "new" (post #342) format, i.e.:Gopkg.toml
Gopkg.lock
without having to do the following?
dep init && dep ensure && dep prune
rm manifest.json; rm lock.json
The text was updated successfully, but these errors were encountered: