From owner-svn-ports-head@FreeBSD.ORG Sat May 30 23:10:02 2015 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6533ADEA; Sat, 30 May 2015 23:10:02 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47C9F10D3; Sat, 30 May 2015 23:10:02 +0000 (UTC) (envelope-from sunpoet@FreeBSD.org) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t4UNA2Dt090248; Sat, 30 May 2015 23:10:02 GMT (envelope-from sunpoet@FreeBSD.org) Received: (from sunpoet@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t4UNA1Hl090246; Sat, 30 May 2015 23:10:01 GMT (envelope-from sunpoet@FreeBSD.org) Message-Id: <201505302310.t4UNA1Hl090246@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: sunpoet set sender to sunpoet@FreeBSD.org using -f From: Sunpoet Po-Chuan Hsieh Date: Sat, 30 May 2015 23:10:01 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r388013 - head/devel/rubygem-icalendar X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2015 23:10:02 -0000 Author: sunpoet Date: Sat May 30 23:10:01 2015 New Revision: 388013 URL: https://svnweb.freebsd.org/changeset/ports/388013 Log: - Add LICENSE - Update pkg-descr - Update WWW Modified: head/devel/rubygem-icalendar/Makefile head/devel/rubygem-icalendar/pkg-descr Modified: head/devel/rubygem-icalendar/Makefile ============================================================================== --- head/devel/rubygem-icalendar/Makefile Sat May 30 23:09:56 2015 (r388012) +++ head/devel/rubygem-icalendar/Makefile Sat May 30 23:10:01 2015 (r388013) @@ -8,6 +8,9 @@ MASTER_SITES= RG MAINTAINER= ruby@FreeBSD.org COMMENT= Library for working with iCalendar files +LICENSE= BSD2CLAUSE GPLv2 RUBY +LICENSE_COMB= dual + USE_RUBY= yes USE_RUBYGEMS= yes RUBYGEM_AUTOPLIST= yes Modified: head/devel/rubygem-icalendar/pkg-descr ============================================================================== --- head/devel/rubygem-icalendar/pkg-descr Sat May 30 23:09:56 2015 (r388012) +++ head/devel/rubygem-icalendar/pkg-descr Sat May 30 23:10:01 2015 (r388013) @@ -1,31 +1,4 @@ -iCalendar -- Internet calendaring, Ruby style +iCalendar is a Ruby library for dealing with iCalendar files in the iCalendar +format defined by RFC-5545. -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: https://github.com/sdague/icalendar +WWW: https://github.com/icalendar/icalendar