[115218] trunk/dports/ruby/rb19-sass/Portfile
Clemens Lang
cal at macports.org
Sun Dec 29 10:17:02 PST 2013
On Sun, Dec 29, 2013 at 10:06:28AM -0800, David Evans wrote:
> On 12/28/13 4:41 AM, cal at macports.org wrote:
> > --- trunk/dports/ruby/rb19-sass/Portfile 2013-12-28 12:34:43 UTC (rev 115217)
> > +++ trunk/dports/ruby/rb19-sass/Portfile 2013-12-28 12:41:50 UTC (rev 115218)
> > @@ -4,9 +4,9 @@
> > PortSystem 1.0
> > PortGroup ruby 1.0
> >
> > -ruby.setup sass 3.2.12 gem {} rubygems ruby19
> > -checksums rmd160 eab4fdb602b96f4ecfd0100bbb76820d25a3ca4c \
> > - sha256 c88d548a265a003d5883ce8b258a3cc523e084a773d5932232dd9ea0220a811c
> > +ruby.setup sass 3.2.13 gem {} rubygems ruby20
> > +checksums rmd160 898fe03a2ff9da54c96f2feb598559ebbcc1e4e7 \
> > + sha256 21bd6adf694014c43ffd668ec3067d52c01623d6b432510b1f3dda1ba342243c
> >
> > description Sass makes CSS fun again.
> > long_description \
> portindex issues (keeps trying to index but fails silently, ruby19 vs
> ruby20?)
>
> $ port lint --nitpick ruby/rb19-sass
> ---> Verifying Portfile for rb20-sass
> Error: Missing required variable: platforms
> Error: Portfile directory rb19-sass does not match port name rb20-sass
> ---> 2 errors and 0 warnings found.
Thanks. I'm not sure how the change to ruby20 slipped in, it certainly
wasn't intentional. Fixed in r115233.
--
Clemens Lang
More information about the macports-changes
mailing list