You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired by your blog post, I'm interested in using the postgres package to do some MySQL<->Postgresql transpiling tasks. However, I found that go build failed with:
After checking the contribution guide, I learned that the parser package relies on some source files generated by doltgresql/postgres/parser/build.sh. However, when importing the package in my project via import "github.com/dolthub/doltgresql/postgres/parser/types", it seems impossible to run the script manually since the go mod cache is a read-only directory:
mkdir: parser/gen: Permission denied
./build.sh: line 12: parser/gen/types_regex.tmp: No such file or directory
Could you consider keeping the generated files in the source tree to make the project more compatible with the standard Go toolchain? This would simplify the build process for users who want to integrate the postgres package into their projects.
I appreciate your time and look forward to your feedback.
The text was updated successfully, but these errors were encountered:
Hi Dolt creators,
Inspired by your blog post, I'm interested in using the
postgres
package to do some MySQL<->Postgresql transpiling tasks. However, I found thatgo build
failed with:After checking the contribution guide, I learned that the parser package relies on some source files generated by
doltgresql/postgres/parser/build.sh
. However, when importing the package in my project viaimport "github.com/dolthub/doltgresql/postgres/parser/types"
, it seems impossible to run the script manually since thego mod
cache is a read-only directory:Could you consider keeping the generated files in the source tree to make the project more compatible with the standard Go toolchain? This would simplify the build process for users who want to integrate the
postgres
package into their projects.I appreciate your time and look forward to your feedback.
The text was updated successfully, but these errors were encountered: