Quoting Georges Khaznadar (2022-11-06 19:55:45) > So, building furo with pure debian tools is possible, and the result > is efficient. I uploaded a new release of package furo to the NEW queue.
Sounds nice. I sure hope you went with sassc. In case you are still in doubt, please let me quote the package short description for ruby-sass: > deprecated CSS compiler - use sassc or ruby-sassc instead Also, I hope you "beautify" CSS files only as part of your examination, not as part of the packaged build where users either will want compact or readable _SASS_ sources. > - you would like to see SASS files distributed under /usr/share/sass; is > it sufficient to shape the packaging so it produces two binary > packages, "furo" for the sphinx style, and "sass-stylesheets-furo" > for SASS stuff? Or would it be sufficient to make a single "furo" > binary, which stores SASS files under /usr/share/sass, and provides a > virtual package name sass-stylesheets-furo? Best would be separate packages: I can easily imagine people wanting to build+serve a custom-styled documentation where content is built using Furo, without needing to pull in Furo-specific dependencies (Python libraries, I guess) which is irrelevant for recompiling SASS or hosting static content. > - you would like to see gumshoe.js packaged separately in Debian. I can > issue an ITP for it. Do you estimate that making a package > node-gumshoe is worth the effort, and the storage cost, for debian > servers? Remember that the flesh in this package is a 500-liner > script. I recommend to discuss with the JavaScript team if more sensible to package it standalone or e.g. include in a collection of small scripts. - 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
signature.asc
Description: signature
