Hello Vincent,
Am 15.08.22 um 19:46 schrieb Vincent Bernat:
It also looks like drf-yasg-nonfree is non-free just because of the
minimized JS files. This is often a problem and while not everybody
agrees with this, you can workaround this issue by shipping the
non-minified sources in debian/missing-sources.
your analysis about the reason is correct.
The specific problem with drf-yasg is that even upstream could not fully
explain how to rebuild or even collect the source files for the
minimized files. This means not that this is solvable, but for me it's
mostly the time factor (but also my nearly zero knowledge about the
node.js universe) to entangle this all. This area is heavily moving
target, unfortunately. It might happen that NetBox is dropping drf-yasg
in favor of some other library.
You may or may not use them in the build process. Maybe it does not
hurt to try to run a minifier (like uglifyjs) on them if you feel
like it. As long as upstream is using the files as is, the FTP
masters are likely to accept a package with the sources in
debian/missing.
I wanted to do exactly this, but this requires a good knowledge what's
going on under the hood. And currently I don't know enough how to get
all these peaces together and if someone with more "how to analyze and
rebuild the minimized JS" knowledge is willing to jump in would be
really appreciated.
If some things are more sorted out I wanted to run the yarn calling
script from the NetBox sources to get some logging about the downloading
of the source files and the kind of all the parts are glued together.
There are some parts of the source for some minimized files are shipped
by the NetBox project. But that's not all.
https://github.com/netbox-community/netbox/tree/develop/netbox/project-static/src
Thanks for your interest and feedback!
--
Regards
Carsten
