kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/net/p5-Google-SAML-Response/Makefile

33 lines
894 B
Makefile
Raw Normal View History

- Convert to new perl framework - Trim Makefile header - Remove MAKE_JOBS_SAFE=yes, it's the default.
2013-08-02 20:52:07 +02:00
# Created by: Gea-Suan Lin <gslin@gslin.org>
Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords. WWW: http://search.cpan.org/dist/Google-SAML-Response/ PR: ports/137445 Submitted by: Gea-Suan Lin <gslin at gslin.org>
2009-08-05 14:24:31 +02:00
# $FreeBSD$
PORTNAME= Google-SAML-Response
- Update to 0.14 - Add LICENSE - Sort PLIST Changes: http://search.cpan.org/dist/Google-SAML-Response/Changes
2015-01-04 18:11:56 +01:00
PORTVERSION= 0.14
Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords. WWW: http://search.cpan.org/dist/Google-SAML-Response/ PR: ports/137445 Submitted by: Gea-Suan Lin <gslin at gslin.org>
2009-08-05 14:24:31 +02:00
CATEGORIES= net perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
- Update to 0.08 - Pass maintainership to perl@ PR: 138044 Submitted by: Gea-Suan Lin <gslin@gslin.org> (maintainer)
2009-08-22 21:22:07 +02:00
MAINTAINER= perl@FreeBSD.org
- Update to 0.14 - Add LICENSE - Sort PLIST Changes: http://search.cpan.org/dist/Google-SAML-Response/Changes
2015-01-04 18:11:56 +01:00
COMMENT= SAML responses for Google SSO implementation
Fix license information for portgs that use "the same license as Perl". Sponsored by: Absolight
2017-09-15 10:58:46 +02:00
LICENSE= ART10 GPLv1+
- Update to 0.14 - Add LICENSE - Sort PLIST Changes: http://search.cpan.org/dist/Google-SAML-Response/Changes
2015-01-04 18:11:56 +01:00
LICENSE_COMB= dual
Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords. WWW: http://search.cpan.org/dist/Google-SAML-Response/ PR: ports/137445 Submitted by: Gea-Suan Lin <gslin at gslin.org>
2009-08-05 14:24:31 +02:00
Fix every instance of RUN_DEPENDS:=${BUILD_DEPENDS} in p5 ports, except for where it resulted in a change in output from build-depends-list or run-depends-list. Approved by: portmgr (adamw)
2018-10-06 15:06:42 +02:00
BUILD_DEPENDS= ${RUN_DEPENDS}
RUN_DEPENDS= p5-Crypt-OpenSSL-Bignum>=0:security/p5-Crypt-OpenSSL-Bignum \
Remove ${PORTSDIR}/ from dependencies, categories m, n, o, and p. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:16:16 +02:00
p5-Crypt-OpenSSL-DSA>=0:security/p5-Crypt-OpenSSL-DSA \
p5-Crypt-OpenSSL-RSA>=0:security/p5-Crypt-OpenSSL-RSA \
p5-File-Which>=0:sysutils/p5-File-Which \
p5-Google-SAML-Request>=0:net/p5-Google-SAML-Request \
p5-HTML-Parser>=0:www/p5-HTML-Parser \
p5-TimeDate>=0:devel/p5-TimeDate \
p5-XML-CanonicalizeXML>=0:textproc/p5-XML-CanonicalizeXML
TEST_DEPENDS= p5-Test-Exception>=0:devel/p5-Test-Exception
Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords. WWW: http://search.cpan.org/dist/Google-SAML-Response/ PR: ports/137445 Submitted by: Gea-Suan Lin <gslin at gslin.org>
2009-08-05 14:24:31 +02:00
- Convert to new perl framework - Trim Makefile header - Remove MAKE_JOBS_SAFE=yes, it's the default.
2013-08-02 20:52:07 +02:00
USES= perl5
- Update to 0.14 - Add LICENSE - Sort PLIST Changes: http://search.cpan.org/dist/Google-SAML-Response/Changes
2015-01-04 18:11:56 +01:00
USE_PERL5= modbuild
Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords. WWW: http://search.cpan.org/dist/Google-SAML-Response/ PR: ports/137445 Submitted by: Gea-Suan Lin <gslin at gslin.org>
2009-08-05 14:24:31 +02:00
Make jobs unsafe on two ports Both of these ports have failed repeatedly under multi-job runs, and had to be fixed by disabling make jobs.
2014-12-15 15:26:05 +01:00
MAKE_JOBS_UNSAFE= yes
Cleanup supporting perl version 5.8 and 5.10, lang/perl5.8 and lang/5.10 will be removed from ports tree soon.
2012-12-17 16:39:36 +01:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink