Skip to content

cr-sqlite is now in the SQLite package registry #296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nalgeon opened this issue Jul 27, 2023 · 2 comments · Fixed by #385
Closed

cr-sqlite is now in the SQLite package registry #296

nalgeon opened this issue Jul 27, 2023 · 2 comments · Fixed by #385
Labels

Comments

@nalgeon
Copy link

nalgeon commented Jul 27, 2023

Hi! I've just added vlcn-io/cr-sqlite to the package registry. It's now available on the website and via the CLI package manager.

No action is required on your part, just a quick heads up.

Thank you for this great extension!

P.S. It would really help though if you could remove the "rename" step, which is not obvious to people and unfortunately not supported by the package manager:

The entrypoint to the loadable extension is sqlite3_crsqlite_init, so you'll either need to provide that to load_extension or rename your binary to crsqlite.[dylib/dll/so].

Extension authors often publish .zip or .tar.gz archives with an extension binary inside, like this:

crsqlite-darwin-x86_64.zip
└─ crsqlite.dylib

crsqlite-darwin-aarch64.zip
└─ crsqlite.dylib

crsqlite-linux-x86_64.zip
└─ crsqlite.so

crsqlite-linux-aarch64.zip
└─ crsqlite.so

crsqlite-windows-x86_64.zip
└─ crsqlite.dll

This way there is no need to rename the binary, and the extension works right after unpacking.

@tantaman
Copy link
Collaborator

Thanks @nalgeon.

I'll update the publish workflow to fix that.

@nalgeon
Copy link
Author

nalgeon commented Oct 13, 2023

Thanks for implementing this change! Looking forward to the next release with zipped assets.

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

Successfully merging a pull request may close this issue.

2 participants