remove x-generate-plist and friends
- use RF macro and remove SUBDIR where possible
- remove some uneeded GEM_NAME=${DISTNAME}
(this c/should be handled better in bsd.*.mk)
other deltas specific to individual ports:
audio/rubygem-mp3info - unbreak, fix packaging, bump PORTREVISION
devel/rubygem-rapt - adopt
devel/rubygem-rspec - remove BUILD_DEPENDS=RUN_DEPENDS -- neither set
devel/rubygem-ruby2ruby - add #' for vim highlight
graphics/rubygem-extifr - drop PORTREVISION=0
graphics/rubygem-gd2 - add #' for vim highlight
www/rubygem-rubyfulsoup - swap GEM_NAME / DISTNAME for constistency
Sponsored by: RideCharge Inc.
Tested on: RideCharge's Tinderbox
Reviewed by: stas
the IP address that is used for polling is replaced with whatever is
defined in ${NAGIOSPOLLIP} (default is 127.0.0.1). If you want to
change this please set it in ports.conf.
PR: ports/133069
Submitted by: L Campbell <llc2w@virginia.edu>
Approved by: Jarrod Sayers <jarrod@netleader.com.au> (maintainer)
Features:
* methods like GET/HEAD/POST/* via HTTP/1.1.
* HTTPS(SSL), Cookies, proxy, authentication(Digest, NTLM, Basic), etc.
* asynchronous HTTP request, streaming HTTP request.
* by contrast with net/http in standard distribution;
o Cookies support
o MT-safe
o streaming POST (POST with File/IO)
o Digest auth
o Negotiate/NTLM auth for WWW-Authenticate (requires net/htlm module)
o NTLM auth for Proxy-Authenticate (requires win32/sspi module)
o extensible with filter interface
o you dont have to care HTTP/1.1 persistent connection (httpclient cares instead of you)
* Not supported now
o Cache
o Rather advanced HTTP/1.1 usage such as Range, deflate, etc. (of course you can set it in header by yourself)
For more detail, see API document at dev.ctor.org/doc/httpclient/
WWW: http://raa.ruby-lang.org/project/httpclient/
Sponsored by: RideCharge Inc.
Extensions of MySql. The data model roughly follows the OGC "Simple i
Features for SQL" specification (see http://www.opengis.org/docs/99-049.pdf),
although without any kind of advanced functionalities (such as geometric
operators or reprojections). It also supports various output and
input formats (GeoRSS, KML, Shapefile).
Sponsored by: RideCharge Inc.
It aims to be as lightweight as possible while still providing core support
for data aggregation and manipulation as well as multi-format rendering
of reports.
Ruport provides tools for using a number of data sources, including CSV files,
ActiveRecord models, and raw SQL connections via RubyDBI (through ruport-util).
Sponsored by: RideCharge Inc.
may spawned locally to take advantage of multiple processors on a single
machine or distributed across many machines to take advantage of distributed
processing.
Sponsored by: RideCharge Inc.
This is a Ruby library for dealing with iCalendar files. Rather than
explaining myself, here is the introduction from RFC-2445, which
defines the format:
The use of calendaring and scheduling has grown considerably in the
last decade. Enterprise and inter-enterprise business has become
dependent on rapid scheduling of events and actions using this
information technology. However, the longer term growth of calendaring
and scheduling, is currently limited by the lack of Internet standards
for the message content types that are central to these knowledgeware
applications. This memo is intended to progress the level of
interoperability possible between dissimilar calendaring and
scheduling applications. This memo defines a MIME content type for
exchanging electronic calendaring and scheduling information. The
Internet Calendaring and Scheduling Core Object Specification, or
iCalendar, allows for the capture and exchange of information normally
stored within a calendaring and scheduling application; such as a
Personal Information Manager (PIM) or a Group Scheduling product.
The iCalendar format is suitable as an exchange format between
applications or systems. The format is defined in terms of a MIME
content type. This will enable the object to be exchanged using
several transports, including but not limited to SMTP, HTTP, a file
system, desktop interactive protocols such as the use of a memory-
based clipboard or drag/drop interactions, point-to-point asynchronous
communication, wired-network transport, or some form of unwired
transport such as infrared might also be used.
WWW: http://rubyforge.org/projects/icalendar/
Sponsored by: RideCharge Inc.
Runt is a Ruby implementation of select Martin Fowler patterns
[http://www.martinfowler.com/articles]. TemporalExpressions allow a developer
to define patterns of date recurrence using set expressions.
Sponsored by: RideCharge Inc.
