"Barak A. Pearlmutter" <[email protected]> writes: > Okay, I picked your commit and made some related modifications. See > collab-maint main branch for details. > > I'm about ready to dput it ... but I sort of feel like a reality check > is needed. Here is my question. > > There is no static (or dynamic) library. (Obviously the build system > could be tweaked to generate them. But it isn't.) Is the -dev package > actually useful without them? If so, could you give a short example? > Just a trivial main program, maybe something that could be put in > /usr/share/doc/scrypt-dev/examples/.
I realized the same after making the -dev package and then trying to use it to remove the embedded code-copy in the python-scrypt package: no shared library. I looked into tweaking the build system to add it, but I realized that probably wasn't a good idea. If upstream isn't willing to maintain a stable API, then we don't want to ship one. I contacted upstream about this, and they didn't seem to think it was worth it. However, I did find another implementation that is currently working on creating a shared library for this purpose. They are not finished with the prospect yet, but indicate that it could be done in a "couple of weeks". I think that with all of that, I would say it is not worth it to provide a -dev package now. micah
pgpXc7J5ySdSs.pgp
Description: PGP signature
