kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/textproc/ruby-json/Makefile

20 lines
494 B
Makefile
Raw Normal View History

Update ruby-json and ruby-json-pure package to 1.8.1. 2013-05-13 (1.8.1) * Remove Rubinius exception since transcoding should be working now.
2014-03-14 19:11:45 +01:00
# $NetBSD: Makefile,v 1.27 2014/03/14 18:11:45 taca Exp $
Initial import of ruby18-json-1.1.2 as textproc/ruby-json. This is a implementation of the JSON specification according to RFC 4627. You can think of it as a low fat alternative to XML, if you want to store data to disk or transmit it over a network rather than use a verbose markup language. The JSON generator escapes all non-ASCII an control characters with \uXXXX escape sequences and supports UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. This means that generated JSON text is encoded as UTF-8 (because ASCII is a subset of UTF-8) and at the same time avoids decoding problems for receiving endpoints that don't expect UTF-8 encoded texts. This package is fast C extension variant which is in parts implemented in C and comes with its own Unicode conversion functions and a parser generated by the Ragel State Machine Compiler.
2008-04-04 17:21:43 +02:00
Update ruby-json and ruby-json-pure package to 1.8.1. 2013-05-13 (1.8.1) * Remove Rubinius exception since transcoding should be working now.
2014-03-14 19:11:45 +01:00
DISTNAME= json-1.8.1
Initial import of ruby18-json-1.1.2 as textproc/ruby-json. This is a implementation of the JSON specification according to RFC 4627. You can think of it as a low fat alternative to XML, if you want to store data to disk or transmit it over a network rather than use a verbose markup language. The JSON generator escapes all non-ASCII an control characters with \uXXXX escape sequences and supports UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. This means that generated JSON text is encoded as UTF-8 (because ASCII is a subset of UTF-8) and at the same time avoids decoding problems for receiving endpoints that don't expect UTF-8 encoded texts. This package is fast C extension variant which is in parts implemented in C and comes with its own Unicode conversion functions and a parser generated by the Ragel State Machine Compiler.
2008-04-04 17:21:43 +02:00
CATEGORIES= textproc
MAINTAINER= pkgsrc-users@NetBSD.org
* Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk. * Update HOMEPAGE. * Remove default value of GEM_BUILD. * Ajust new ruby package's framework.
2010-09-10 10:18:49 +02:00
HOMEPAGE= http://flori.github.com/json
Initial import of ruby18-json-1.1.2 as textproc/ruby-json. This is a implementation of the JSON specification according to RFC 4627. You can think of it as a low fat alternative to XML, if you want to store data to disk or transmit it over a network rather than use a verbose markup language. The JSON generator escapes all non-ASCII an control characters with \uXXXX escape sequences and supports UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. This means that generated JSON text is encoded as UTF-8 (because ASCII is a subset of UTF-8) and at the same time avoids decoding problems for receiving endpoints that don't expect UTF-8 encoded texts. This package is fast C extension variant which is in parts implemented in C and comes with its own Unicode conversion functions and a parser generated by the Ragel State Machine Compiler.
2008-04-04 17:21:43 +02:00
COMMENT= Native extension implementation of JSON for Ruby
Update ruby-json to 1.2.0 Too many changes, see: http://github.com/flori/json/blob/master/CHANGES
2009-11-23 14:33:47 +01:00
LICENSE= ruby-license
Set USE_GCC_RUNTIME=yes for packages which build shared libraries but do not use libtool to do so. This is required to correctly depend upon a gcc runtime package (e.g. gcc47-libs) when using USE_PKGSRC_GCC_RUNTIME.
2014-03-13 12:08:49 +01:00
USE_GCC_RUNTIME= yes
Fixes GEM_CLEANBUILD patterns, or built C extensions are cleared and result in same as ruby-json-pure. Bump PKGREVISION.
2010-06-15 15:35:52 +02:00
GEM_CLEANBUILD= ext/json/ext/generator/* ext/json/ext/parser/*
Initial import of ruby18-json-1.1.2 as textproc/ruby-json. This is a implementation of the JSON specification according to RFC 4627. You can think of it as a low fat alternative to XML, if you want to store data to disk or transmit it over a network rather than use a verbose markup language. The JSON generator escapes all non-ASCII an control characters with \uXXXX escape sequences and supports UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. This means that generated JSON text is encoded as UTF-8 (because ASCII is a subset of UTF-8) and at the same time avoids decoding problems for receiving endpoints that don't expect UTF-8 encoded texts. This package is fast C extension variant which is in parts implemented in C and comes with its own Unicode conversion functions and a parser generated by the Ragel State Machine Compiler.
2008-04-04 17:21:43 +02:00
Update ruby-json pacakge to 1.1.3. 2008-07-10 (1.1.3) * Wesley Beary <monki@geemus.com> reported a bug in json/add/core's DateTime handling: If the nominator and denominator of the offset were divisible by each other Ruby's Rational#to_s returns them as an integer not a fraction with '/'. This caused a ZeroDivisionError during parsing. * Use Date#start and DateTime#start instead of sg method, while remaining backwards compatible. * Supports ragel >= 6.0 now. * Corrected some tests. * Some minor changes.
2008-09-15 10:38:01 +02:00
post-extract:
cd ${WRKSRC}; ${FIND} . -xdev -type f -print | ${XARGS} ${CHMOD} g-w
* Use lang/ruby/gem.mk instead of misc/rubygems/rubygem.mk. * Update HOMEPAGE. * Remove default value of GEM_BUILD. * Ajust new ruby package's framework.
2010-09-10 10:18:49 +02:00
.include "../../lang/ruby/gem.mk"
Initial import of ruby18-json-1.1.2 as textproc/ruby-json. This is a implementation of the JSON specification according to RFC 4627. You can think of it as a low fat alternative to XML, if you want to store data to disk or transmit it over a network rather than use a verbose markup language. The JSON generator escapes all non-ASCII an control characters with \uXXXX escape sequences and supports UTF-16 surrogate pairs in order to be able to generate the whole range of Unicode code points. This means that generated JSON text is encoded as UTF-8 (because ASCII is a subset of UTF-8) and at the same time avoids decoding problems for receiving endpoints that don't expect UTF-8 encoded texts. This package is fast C extension variant which is in parts implemented in C and comes with its own Unicode conversion functions and a parser generated by the Ragel State Machine Compiler.
2008-04-04 17:21:43 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink