devel/rubygem-icalendar: Update to 2.12.4 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.mdd7ea47c69f
Port details
devel/rubygem-icalendar2.12.4
Library for working with iCalendar files
- Maintainer
- ruby@FreeBSD.org
- Packages
- rubygem-icalendar 2.12.4
- Upstream
- Higher version available: 2.13.0
- CPE
icalendar_project:icalendarfrom the port- WWW
- https://github.com/icalendar/icalendar
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (48)
devel/rubygem-icalendar: Add CPE information5eceea68de
devel/rubygem-icalendar: Update to 2.12.3 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md7caced1365
devel/rubygem-icalendar: Update to 2.12.2 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md9e0292a79d
devel/rubygem-icalendar: Update to 2.12.1 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md753218cde5
devel/rubygem-icalendar: Update to 2.12.0 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.mdc81b8f4305
devel/rubygem-icalendar: Update to 2.11.2 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md6966328cd2
devel/rubygem-icalendar: Update to 2.11.1 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md8109ca2cbf
devel/rubygem-icalendar: Update to 2.11.0 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.md4a0c34201e
devel/rubygem-icalendar: Update to 2.10.3 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.mdccc80fc093
devel/rubygem-icalendar: Update to 2.10.2 Changes: https://github.com/icalendar/icalendar/blob/main/CHANGELOG.mdde8e895a4d
devel/rubygem-icalendar: Update to 2.10.1 Changes: https://github.com/icalendar/icalendar/blob/main/History.txt1ed538169b
devel/rubygem-icalendar: Update to 2.10.0 Changes: https://github.com/icalendar/icalendar/blob/main/History.txt82c66d19ac
devel/rubygem-icalendar: Update to 2.9.0 Changes: https://github.com/icalendar/icalendar/blob/main/History.txtdd41d9b9bc
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D3792518c6e18276Remove WWW entries moved into port Makefiles Commit b7f05445c00f has added WWW entries to port Makefiles based on WWW: lines in pkg-descr files. This commit removes the WWW: lines of moved-over URLs from these pkg-descr files. Approved by: portmgr (tcberner)fb16dfecae
Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)b7f05445c0
devel/rubygem-icalendar: Update to 2.8.0 - Update LICENSE Changes: https://github.com/icalendar/icalendar/blob/main/History.txt7beddb4ff1
devel/rubygem-icalendar: Update to 2.7.1 Changes: https://github.com/icalendar/icalendar/blob/master/History.txtffcf017630
One more small cleanup, forgotten yesterday. Reported by: lwhsucf118ccf87
Remove # $FreeBSD$ from Makefiles.305f148f48
Update to 2.6.1 - Update version requirement of RUN_DEPENDS Changes: https://github.com/icalendar/icalendar/blob/master/History.txt17c027f356
Update to 2.5.3 Changes: https://github.com/icalendar/icalendar/blob/master/History.txtb9c3551184
Update to 2.5.2 Changes: https://github.com/icalendar/icalendar/blob/master/History.txt1afff3c97b
Update to 2.5.1 Changes: https://github.com/icalendar/icalendar/blob/master/History.txte4b322b3f2
Update to 2.5.0 Changes: https://github.com/icalendar/icalendar/blob/master/History.txt33c7a127e1
devel/rubygem-icalendar: update to 2.4.1273d14fa26
Convert USES=gem:autoplist to USES=gem since autoplist is default462519941e
create USES=gem and update rubygem- ports to use it Note that for now ports still have to have USE_RUBY=yes to use USES=gem PR: 209041 Differential Revision: https://reviews.freebsd.org/D6070b3e8fe8d85
Set NO_ARCH for remaining rubygem-* ports with no arch dependent files Obtained from: DEVELOPER_MODE With Hat: ruby@ Sponsored by: RideCharge Inc / Curb4e3d011569
- Update to 2.3.0 Changes: https://github.com/icalendar/icalendar/blob/master/History.txt6871bcc92c
- Add LICENSE - Update pkg-descr - Update WWWbb6654eec7
devel/rubygem-icalendar: 2.1.25f45497c22
devel/rubygem-icalendar: update to 2.1.1067b74edc9
- Add stage support8cb915da41
Add NO_STAGE all over the place in preparation for the staging support (cat: devel part 4)77d32abc6b
- Update to 1.4.1f686958d2b
- Update to 1.4.046b381933d
- Update to 1.2.1a51e2bc6c6
- Add COMMENTafdfe39f83
- Update to 1.1.679271af98a
- github is redirecting all these to https now60ca7e308f
- Mass fixup of WWW: lines pkg-descr based on rubygems.org Homepage meta info Prompted by: distilator With Hat: ruby@ Sponsored by: RideCharge Inc. / TaxiMagic7b05323e04
- Update to 1.1.516aacad6f0
- Mass conversion of RF -> RG for MASTER_SITE for rubygem- ports [RG aka rubygems.org] PR: ports/147005 Submitted by: pgollucci (myself) Approved by: portmgr (pav) With Hat: ruby@8f3a51419c
- Re-assign all my rubygem-* ports to ruby@ this gives us more eyes and brings us inline with perl@ Current ruby@ members (stas, dinoex, pgollucci) http://wiki.freebsd.org/Ruby Discussed with: stas on #bsdportsa0461d68d5
- Update to 1.1.4d7133b568b
iCalendar -- Internet calendaring, Ruby style 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.02aceb5555