Includes possible non-free content about breadability

[mitechie]

So just to make sure, this is in reference to the web content used for test cases that we have? Would something like moving the tests out of the actual package help/hurt the cause? We could try to 'make up' content that fits the test case, but it's obviously important that once we hit a bug it's easy/best to get that content and make sure we parse it correctly.

[jelmer]

On Sat, Apr 12, 2014 at 10:36:24AM -0700, Rick Harding wrote:

So just to make sure, this is in reference to the web content used for test cases that we have? Would something like moving the tests out of the actual package help/hurt the cause? We could try to 'make up' content that fits the test case, but it's obviously important that once we hit a bug it's easy/best to get that content and make sure we parse it correctly.
Yep, it's about the web content. Moving it out of the actual package
would help a lot, because that means I can just package the upstream
source without the tests.

Making up contents would be ideal (because it means I can still run
the tests for every package build), but I'm guessing is also the most
work.

Cheers,

Jelmer

[mitechie]

Ok cool, I'll try to pull the tests out as that'll be fast and unblock you and then can see if we can mimic the issue the site gave us and replicate it in a 'generic' way as follow ups.

[mitechie]

I've uploaded 0.1.20 that does not include the tests in the source build. We'll keep that as a pure development tool for now and use in CI while we try to find a better way to generate test files that aren't copyrighted material.

[jelmer]

Thanks!