Hello Jonas then you for your custody, *all* sources are contained in the upstream package, copyright owners and license details are in the file debian/copyright. webpack is currently a debian-supported compiler package, however it misses currently quite a few plugins which were used by the upstream author. When I ran manually `npm install .`, I added this missing software: so when `webpack build --mode development` was called, it could be considered as a black box, which does not fit your conviction, neither mine. However this black box took human-readable source files (SASS source files and JS scripts) and created human-readable target files (CSS files and JS scripts). I read those output files, compared them with source files: FS scripts contain the same code, with some parts gathered in a common file, and CSS files are readable too. If you wan to read the files too, please feel free to check them, the more eyeballs, the less errors. In the "binary" pachage furo, those files can be found as: - source SASS files: under /usr/lib/python3/dist-packages/furo/assets/styles/ please notice that the file /usr/share/javascript/normalize.css/normalize.css is also a source, it is "included". This file comes from the package node-normalize.css - source JS files: under /usr/lib/python3/dist-packages/furo/assets/scripts/ - "binaries": all CSS files are under /usr/lib/python3/dist-packages/furo/theme/furo/static/styles/; please have a look at them as I did. Their content is a straight interpretation of source SASS files. All JS files are under /usr/lib/python3/dist-packages/furo/theme/furo/static/scripts; please have a look at them as I did. They are actually gathering source code coming from the directory assets/scripts. This is why I believe that this furo package obeys Debian Policy § 2.1: "The program must include source", because source code is there, and because CSS and JS files resulting from the manual process are fully human readable. Best regards, Georges. Jonas Smedegaard a écrit : > [resent using X-Debbugs-Cc to circumvent orange.fr SPF blockage ] > > Quoting Georges Khaznadar (2022-11-04 18:07:41) > > I just uploaded a furo package to experimental (via the NEW queue). > > Here is how I made missing files, working around a few inconveniences: > > > > - as webpack could not be used in a pbuilder chroot to do the job, due > > to missing nodejs packages, I ran `npm install .` and > > `webpack build --mode development`, to compile the SASS files, and > > to pack the Javascript sources, with *no obfuscation*. Then I removed > > the directory node_modules/, and collected the output of webpack to > > make a debian patch, with quilt. > > > > - the metadata were also collected manually (with `pip install furo` in > > a clean chroot): as they contain no obfuscated files, they could be > > also be collected as a debian patch. > > > > Of course, the NodeJS things required to build the CSS may be very > > useful when then enter Debian, so Andrey Rahmatullin's RFPs are welcome. > > Thanks for elaborating on your preliminary work, Georges. > > Please beware that what you describe as "a few inconveniences" sounds > like violations of Debian Policy § 2.1: "The program must include source > code". > > This must includes also code released to the experimental branch of > Debian. > > Please remove all code that is build from sources non-Debian source. > > > Kind regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > * Sponsorship: https://ko-fi.com/drjones > > [x] quote me freely [ ] ask before reusing [ ] keep private -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
Attachment:
signature.asc
Description: PGP signature