2016-06-08 21:22:13 +02:00
|
|
|
# $NetBSD: Makefile,v 1.13 2016/06/08 19:23:57 wiz Exp $
|
Add p5-IMAP-Client-0.13 (and its small dependency, p5-URI-imap).
From DESCR:
This module was created as a low-level inteface to any IMAP server. It
was built to be a 'clear box' solution to working with an IMAP environ-
ment. The idea is that anything an IMAP client should be able to do,
and any information available via the IMAP specs, should be available
to a client interface and user. This way, the full strength of the
IMAP protocol and data can be utilized, ideally in the most network-
efficient mannger possible, rather than being contrained only to a sub-
set of commands or data-limited responses. If the server says it, the
client should be able to see it.
This module also takes steps to be able to handle anticipated situa-
tions for the user rather than forcing a per-implementation behavior
for such expected events, such as referrals. IMAP::Client will fully
support referrals, and will transparently handle them for whatever com-
mand is issued to them (so long as the referral s for anonymous or the
same user with the same password - a new user or different password
would require a new username/password to be obtained. As of 0.01, this
is not supported, however the framework is down.
This module also tries to follow the various RFCs for IMAPrev1 communi-
cations very closely, enforcing client-side responsabilities where
appropriate.
2007-10-11 17:49:55 +02:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
DISTNAME= IMAP-Client-0.13
|
|
|
|
|
PKGNAME= p5-${DISTNAME}
|
2016-06-08 21:22:13 +02:00
|
|
|
PKGREVISION= 9
|
Add p5-IMAP-Client-0.13 (and its small dependency, p5-URI-imap).
From DESCR:
This module was created as a low-level inteface to any IMAP server. It
was built to be a 'clear box' solution to working with an IMAP environ-
ment. The idea is that anything an IMAP client should be able to do,
and any information available via the IMAP specs, should be available
to a client interface and user. This way, the full strength of the
IMAP protocol and data can be utilized, ideally in the most network-
efficient mannger possible, rather than being contrained only to a sub-
set of commands or data-limited responses. If the server says it, the
client should be able to see it.
This module also takes steps to be able to handle anticipated situa-
tions for the user rather than forcing a per-implementation behavior
for such expected events, such as referrals. IMAP::Client will fully
support referrals, and will transparently handle them for whatever com-
mand is issued to them (so long as the referral s for anonymous or the
same user with the same password - a new user or different password
would require a new username/password to be obtained. As of 0.01, this
is not supported, however the framework is down.
This module also tries to follow the various RFCs for IMAPrev1 communi-
cations very closely, enforcing client-side responsabilities where
appropriate.
2007-10-11 17:49:55 +02:00
|
|
|
CATEGORIES= mail perl5
|
|
|
|
|
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=IMAP/}
|
|
|
|
|
|
|
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
|
|
|
|
COMMENT= Perl5 module for IMAP manipulation
|
|
|
|
|
|
|
|
|
|
DEPENDS+= p5-IO-Socket-SSL>=0:../../security/p5-IO-Socket-SSL
|
2015-07-12 20:56:06 +02:00
|
|
|
#DEPENDS+= {perl>=5.7.3,p5-MIME-Base64>=0}:../../converters/p5-MIME-Base64
|
Add p5-IMAP-Client-0.13 (and its small dependency, p5-URI-imap).
From DESCR:
This module was created as a low-level inteface to any IMAP server. It
was built to be a 'clear box' solution to working with an IMAP environ-
ment. The idea is that anything an IMAP client should be able to do,
and any information available via the IMAP specs, should be available
to a client interface and user. This way, the full strength of the
IMAP protocol and data can be utilized, ideally in the most network-
efficient mannger possible, rather than being contrained only to a sub-
set of commands or data-limited responses. If the server says it, the
client should be able to see it.
This module also takes steps to be able to handle anticipated situa-
tions for the user rather than forcing a per-implementation behavior
for such expected events, such as referrals. IMAP::Client will fully
support referrals, and will transparently handle them for whatever com-
mand is issued to them (so long as the referral s for anonymous or the
same user with the same password - a new user or different password
would require a new username/password to be obtained. As of 0.01, this
is not supported, however the framework is down.
This module also tries to follow the various RFCs for IMAPrev1 communi-
cations very closely, enforcing client-side responsabilities where
appropriate.
2007-10-11 17:49:55 +02:00
|
|
|
DEPENDS+= p5-URI-imap>=0:../../mail/p5-URI-imap
|
|
|
|
|
DEPENDS+= p5-URI>=0:../../www/p5-URI
|
|
|
|
|
|
|
|
|
|
USE_LANGUAGES= # empty
|
|
|
|
|
PERL5_PACKLIST= auto/IMAP/Client/.packlist
|
|
|
|
|
|
|
|
|
|
.include "../../lang/perl5/module.mk"
|
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|
