Michał Górny
Michał Górny
> Is there any problem with releasing the source code (not the binary package) under ISC? Note that Fbpdf is under ISC now. To the best of my knowledge, yes....
Maybe a bit more explanation is in place. The idea behind GPL/AGPL is that GPL-ed software must never ever be used in proprietary software. That's why these licenses require that...
Well, your previous suggestion of dual-licensing makes sense to me. However, if you go that way, please make it explicitly clear that when linking to AGPL-licensed versions of mupdf (doubt...
I've done some research and I was wrong a bit. I'm sorry for that. According to https://www.gnu.org/licenses/gpl-faq.en.html#IfLibraryIsGPL, it's fine to release all sources as ISC, and then only indicate that...
Yes, we'll handle the right deps ourselves, as well as stripping `simdjson.h` to ensure linking against the system header (I couldn't think of an easy way to do that).
I see that #303 addresses a part of the problem, and its solution seems to be simpler.
I don't think so. It's basically the same (wrong?) solution, just done in a more verbose way.
These would be, as of 0.8.1: ``` tests/integration/test_hooks.py tests/integration/test_placeholders.py tests/integration/test_record_modes.py except for TestRecordNone tests/integration/test_unicode.py tests/regression/test_gzip_compression.py tests/regression/test_requests_2_11_body_matcher.py ``` Of course, it would be better to run them against a locally-spawned server,...
Hmm, that actually seems valid LESS and `lessc` seems to handle it just fine.