clarifying license situation

[alexanderkjall]

I'm looking at packaging this for Debian, and the section in the readme about the license situation is a bit unclear to me.

Does "Our tests include third-party code and data. The benchmarking code includes third-party code" mean that this code is not licensed under a free license? Or does it simply mean that the copyright holder for the benchmark and test code isn't the same as the rest of the code?

[anonrig]

Benchmarks and tests are not distributed with the code. Only the source code. And the license is dual: MIT/Apache2.

[anonrig]

cc @lemire

[alexanderkjall]

If I look in distributed artifact ( https://docs.rs/crate/ada-url/latest/source/ ), there is a directory called "bench" and one that is called "tests".

Do the "benchmarks and tests" refer so something else than these directories?

[lemire]

@alexanderkjall When a Rust library calls in developer dependencies using cargo, these dependencies are not covered by the license of the authors. It is always so. And I suspect that the vast majority of Rust libraries have dev dependencies.

We license the library. What constitutes the library should be clear. It is what people use as a dependency. It is a well defined concept within the scope of Rust/cargo project. There should be no ambiguity.

If you want to distribute the tests or the benchmarks, then you bring in additional software and data that's not covered. For example, there are software dependencies. Further, the tests run on WPT data which we do not own.

I believe that this is 100% industry standard. This is what it means to license a library.

What we are saying is that if you include the library made available by this project, to Debian users, then the result is covered by the authors' license.