- Add LICENSE
- Update pkg-descr - Update WWW
This commit is contained in:
parent
18e501a001
commit
bb6654eec7
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=388013
2 changed files with 6 additions and 30 deletions
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue