[...]
I think this is perfectly fine and I don't see much benefit in combining the CSS and JS files at build-time. It would allow to drop the django-compressor dependency but with the cost of more heavy build-time adjustments that need to be maintained in future.
I agree, the extra gain by this would be minimal at a rather high maintenance cost.
So I'm happy to now have a solution to drop both node-less and sassc from runtime dependencies in the Debian package. Thanks to everyone for their input on this topic.
Thank you so much!
I think that also eases the maintenance of a live mailman deployment having much less complex components installed.
I understand that this won't be for Buster. Just curious for related Ubuntu planning - are you planning to do an upload to experimental ahead of time or are you waiting until Buster is released?
I added a comment to upstream hyperkitty issue #120 where I proposed to do the same in the upstream hyperkitty release process and that way get rid of the sassc runtime dependency:
https://gitlab.com/mailman/hyperkitty/issues/120#note_179256370
Great, that will help to keep things in sync.