You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, it might be interesting to use libraries with release-incompatible licenses in [dev-dependencies]. One example would be dssim, which is licensed under AGPL, and can be useful for comparing graphical output to a reference image while tolerating minor visually-invisible differences. In this case, its license doesn't need to be considered for the final binary release since neither the code nor any of its output will be included in it.
In deny.toml, the interface for this could be to simply have an additional allow-dev section. Like below:
dev-allow would implicitly include everything from allow, since I can't really imagine a case where a library would not be OK to use for local tests, but OK in a final binary.
The text was updated successfully, but these errors were encountered:
Sometimes, it might be interesting to use libraries with release-incompatible licenses in
[dev-dependencies]
. One example would bedssim
, which is licensed under AGPL, and can be useful for comparing graphical output to a reference image while tolerating minor visually-invisible differences. In this case, its license doesn't need to be considered for the final binary release since neither the code nor any of its output will be included in it.In deny.toml, the interface for this could be to simply have an additional
allow-dev
section. Like below:dev-allow
would implicitly include everything fromallow
, since I can't really imagine a case where a library would not be OK to use for local tests, but OK in a final binary.The text was updated successfully, but these errors were encountered: