I have no problem with distros generating CSS files however they like;
overriding what stylesheet is included is trivial and already quite possible. If
that's a viable solution for distros who don't currently support node.js I'm all
for it. Documenting what those distros would need to do would be a compromise
I'm more than happy with... ;-)

- Gabriel

From: Kiall Mac Innes [mailto:kia...@managedit.ie] Sent: Friday, May 25, 2012 11:41 AM To: Gabriel Hurley Cc: open...@lists.launchpad.net Subject: Re: [Openstack] Nodejs in horizon

On Fri, May 25, 2012 at 11:27 AM, Gabriel Hurley
<Gabr...@nebula.com<mailto:Gabr...@nebula.com>> wrote:

4. LESS for dev, commit compiled files: I veto'd this one in Horizon's
discussions. I've played this game being a committer for Django when we tried to
maintain both "development" and "production" versions of the admin's javascript
files. It was a nightmare trying to do due diligence on contributions to make
sure they were always in sync, etc. It's also an added burden on the developers
to understand this process and always adhere to updating both files. All in all,
not a scenario I support in any way shape or form.

Is there another option that has been overlooked? using less.js in development,
and providing a flag to switch to using a pre-compiled file.

At that point, the .css file can be generated by either the tarball script on
Jenkins, or by the distro's themselves however they wish.

Thanks, Kiall