On Sun, Jul 12, 2015 at 6:12 AM, frantisek holop <min...@obiit.org> wrote:
> Jeremy Evans, 05 Feb 2015 16:15: > > On Thu, Feb 5, 2015 at 1:45 PM, frantisek holop <min...@obiit.org> > wrote: > > > > > another go at this port, version 3.4.11 > > > this is a port for http://sass-lang.com/ > > > a program to process scss files. > > > > > > $ cat pkg/DESCR > > > Sass makes CSS fun again. Sass is an extension of CSS3, > > > adding nested rules, variables, mixins, selector inheritance, > > > and more. It's translated to well-formatted, standard CSS > > > using the command line tool or a web-framework plugin. > > > > > > > > > please test and commit. > > > > > > > This still FLAVORs the port, and suffixes the executables with the > related > > ruby version. Last time you posted this I explained that it shouldn't do > > either, since it is being added for the executable only and not to be > > usable as a ruby library. > > > > Please look at the sysutils/god port for an example. You'll want at > least: > > > > MODRUBY_HANDLE_FLAVORS = No > > GEM_FLAGS = --no-format-executable > > updated according to your requirements. > please test and commit. > CONFIGURE_STYLE should be "ruby gem" instead of "ruby gem ext", since this doesn't include a C extension. It doesn't even package for me with "ruby gem ext". However, other than that, the port looks and works fine. Can I get an OK from another developer to import this with the CONFIGURE_STYLE fix? Thanks, Jeremy
