kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/print/rubygem-color/Makefile

20 lines
427 B
Makefile
Raw Normal View History

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 13:18:01 +01:00
# $FreeBSD$
PORTNAME= color
- Update to 1.4.2
2013-07-13 21:40:18 +02:00
PORTVERSION= 1.4.2
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 13:18:01 +01:00
CATEGORIES= print rubygems
- RF -> RG conversions With Hat: ruby@
2010-10-05 11:09:18 +02:00
MASTER_SITES= RG
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 13:18:01 +01:00
- set MAINTAINER ro ruby@
2012-06-29 06:07:49 +02:00
MAINTAINER= ruby@FreeBSD.org
- Fix typos in COMMENT - Enforce the now clarified rules from the Porter's Handbook (e.g. no dots, no A/An, etc.)
2012-08-02 11:02:43 +02:00
COMMENT= Provides colour space definition and manipulation
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 13:18:01 +01:00
- 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 21:25:10 +02:00
RUN_DEPENDS= rubygem-archive-tar-minitar>=0.5.1:${PORTSDIR}/archivers/rubygem-archive-tar-minitar \
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 13:18:01 +01:00
rubygem-hoe>=1.3.0:${PORTSDIR}/devel/rubygem-hoe
- 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 10:58:21 +02:00
USE_RUBY= yes
USE_RUBYGEMS= yes
- Fix plist after ruby update by generating it dynamically.
2009-02-14 02:31:15 +01:00
RUBYGEM_AUTOPLIST= yes
- 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 10:58:21 +02:00
Add NO_STAGE all over the place in preparation for the staging support (cat: print)
2013-09-21 00:43:59 +02:00
NO_STAGE= yes
- 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 10:58:21 +02:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink