[kwlug-disc] Presentation requests: package formats, repository best practices

[Doug Moen]

> Building Curv on Windows might be an interesting opportunity to learn
> Choclaty. [1]
> 
> [1] https://chocolatey.org/

Hmm, interesting. I haven't investigated Chocolatey. The next stage of my plan for Windows was to build a statically linked 'curv.exe' executable (no DLLs), and bundle that in a ZIP file with library  files, examples and documentation. And then make the ZIP file available for download from Github. The ZIP file would be built using a github actions script. There is some work to be done before Curv can be statically linked on Windows. The reason for static linking is that Curv is a command line tool, which your shell (cmd.exe, power shell, bash.exe) needs to locate in the PATH. I don't want to put Curv DLLs in the PATH to avoid conflicts with other software.

More discussion here: https://github.com/curv3d/curv/issues/97

> This would be a library level package manager for the Curv language?
> (e.g., I have a curv program that uses library x,y, and z. I add those
> in my specification file, and then I can run "gpkg install" to install
> all the libraries.)

Yes.