diff --git a/devel/Makefile b/devel/Makefile index 8a91ccdb20c6a..bcc3cc22fa1d8 100644 --- a/devel/Makefile +++ b/devel/Makefile @@ -5591,6 +5591,7 @@ SUBDIR += py-wsgitools SUBDIR += py-wsgiutils SUBDIR += py-wsme + SUBDIR += py-x-wr-timezone SUBDIR += py-xarray SUBDIR += py-xarray-einstats SUBDIR += py-xarray-simlab diff --git a/devel/py-x-wr-timezone/Makefile b/devel/py-x-wr-timezone/Makefile new file mode 100644 index 0000000000000..93c5e891c889c --- /dev/null +++ b/devel/py-x-wr-timezone/Makefile @@ -0,0 +1,23 @@ +PORTNAME= x-wr-timezone +PORTVERSION= 0.0.5 +CATEGORIES= devel python +MASTER_SITES= CHEESESHOP +PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} +DISTNAME= x_wr_timezone-${PORTVERSION} + +MAINTAINER= sunpoet@FreeBSD.org +COMMENT= Python module and program to convert calendars using X-WR-TIMEZONE to standard ones +WWW= https://pypi.org/project/x-wr-timezone/ + +LICENSE= LGPL3+ +LICENSE_FILE= ${WRKSRC}/LICENSE + +RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}icalendar>=0:devel/py-icalendar@${PY_FLAVOR} \ + ${PYTHON_PKGNAMEPREFIX}pytz>=0,1:devel/py-pytz@${PY_FLAVOR} + +USES= python:3.5+ +USE_PYTHON= autoplist concurrent distutils + +NO_ARCH= yes + +.include diff --git a/devel/py-x-wr-timezone/distinfo b/devel/py-x-wr-timezone/distinfo new file mode 100644 index 0000000000000..26e38f94e2094 --- /dev/null +++ b/devel/py-x-wr-timezone/distinfo @@ -0,0 +1,3 @@ +TIMESTAMP = 1674588058 +SHA256 (x_wr_timezone-0.0.5.tar.gz) = c05cb34b9b58a4607a788db086dcae5766728e4b94e0672870dc5593a6e13fe6 +SIZE (x_wr_timezone-0.0.5.tar.gz) = 15479 diff --git a/devel/py-x-wr-timezone/pkg-descr b/devel/py-x-wr-timezone/pkg-descr new file mode 100644 index 0000000000000..e21ec8a6dbc71 --- /dev/null +++ b/devel/py-x-wr-timezone/pkg-descr @@ -0,0 +1,8 @@ +Some calendar providers introduce the non-standard X-WR-TIMEZONE parameter to +ICS calendar files. Strict interpretations according to RFC 5545 ignore the +X-WR-TIMEZONE parameter. This causes the times of the events to differ from +those which make use of X-WR-TIMEZONE. + +This module aims to bridge the gap by converting calendars using X-WR-TIMEZONE +to a strict RFC 5545 calendars. So, let's put our heads together and solve this +problem for everyone!