5 Commits

Author	SHA1	Message	Date
Philip M. Gollucci	843ade1030	- GEMS are always RUN_DEPENDS of other GEMS ... - Bump PORTREVISION when something other then BUILD_DEPENDS changes - Some minor verticle whitespace in some ports for consistency with the rest PR: ports/147551 Submitted by: pgollucci@ (myself) Reviewed by: portmgr (pav) With Hat: ruby	2010-06-06 19:25:10 +00:00
Dirk Meyer	b2c24fbffd	- update to 1.4.1	2010-02-11 13:25:53 +00:00
Stanislav Sedov	72a5a24477	- Fix plist after ruby update by generating it dynamically.	2009-02-14 01:31:15 +00:00
Stanislav Sedov	fae8e0f615	- Add ruby 1.9 support ... - Implement new knobs for gems and rake (these are included in ruby 1.9 distribution already). Also move gem bits from ruby-gems/Makefile.common to bsd.ruby.mk[1]. Now to depend on gems or rake you should define USE_RUBYGEMS/USE_RAKE accordingly. Also RAKE_BIN variable is provided for pointing to the right rake executable. - Rewrite RUBY_SCHEBANG in awk to eliminate build dependency on ruby. Discussed with: Jonathan Weiss <jw@innerewut.de> [1] (gems maintainer) Tested by: ports@	2008-04-06 08:58:21 +00:00
Dirk Meyer	2672c4bbb1	The capabilities of the Color library are limited to pure mathematical ... manipulation of the colours based on colour theory without reference to colour profiles (such as sRGB or Adobe RGB). For most purposes, when working with the RGB and HSL colours, this won't matter. However, some colour models (like CIE L*a*b*) are not supported because Color does not yet support colour profiles, giving no meaningful way to convert colours in absolute colour spaces (like L*a*b*, XYZ) to non-absolute colour spaces (like RGB). WWW: http://rubyforge.org/projects/color/	2008-03-29 12:18:01 +00:00