Package: wnpp Severity: wishlist
* Package name : libsass Version : 1.0 Upstream Author : Hampton Catlin <supp...@moovweb.com> * URL : https://github.com/hcatlin/libsass * License : BSD Programming Lang: C, C++ Description : A C implementation of a Sass compiler Actually, i wonder if we should provide libsass as a seperate package shared with sass-compiler, python-sass, etc. or let each bindings link statically to libsass. I prefer shipping one .so and have package for sass-compiler, python-sass, and ruby-sass using the shared object. We could still ship libsass.a in libsass-dev for static linking. FROM libsass project : Libsass is a C/C++ port of the Sass CSS precompiler. The original version was written in Ruby, but this version is meant for efficiency and portability. Sass is a CSS pre-processor language to add on exciting, new, awesome features to CSS. Sass was the first language of its kind and by far the most mature and up to date codebase. Sass was originally created by the co-creator of this library, Hampton Catlin (@hcatlin). The extension and continuing evolution of the language has all been the result of years of work by Nathan Weizenbaum (@nex3) and Chris Eppstein (@chriseppstein). For more information about Sass itself, please visit http://sass-lang.com -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121129155331.1410.84404.reportbug@web-dev.bersace.local
