Failed plenv install-cpanm and ended up installing curl with --with-openssl option

Today I tried `plenv install-cpanm` and it failed. I do remember it worked fine a couple of month ago and the only thing I can think of was that I did `yum update openssl` last month. I'm pretty sure I didn't do anything else nasty.

	% plenv install-cpanm
	% Total % Received % Xferd Average Speed Time Time Time Current
	Dload Upload Total Spent Left Speed
	113 226 113 226 0 0 144 0 0:00:01 0:00:01 --:--:-- 144
	Bareword found where operator expected at - line 3, near "400 Bad"
	(Missing operator before Bad?)
	Bareword found where operator expected at - line 6, near "<p>Your"
	(Missing operator before Your?)
	syntax error at - line 2, near "html>"
	Execution of - aborted due to compilation errors.

view raw gistfile1.txt hosted with ❤ by GitHub

I searched and found someone with same problem. I followed what he did as shown below:

	% curl --version
	curl 7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.13.6.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
	Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
	Features: GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

view raw gistfile1.txt hosted with ❤ by GitHub

	wget http://curl.haxx.se/download/curl-7.36.0.tar.gz
	tar zxvf curl-7.36.0.tar.gz
	cd curl-7.36.0
	./configure --prefix=/usr/local --with-openssl
	configure: Configured to build curl/libcurl:
	curl version: 7.36.0
	Host setup: x86_64-unknown-linux-gnu
	Install prefix: /usr/local
	Compiler: gcc
	SSL support: enabled (OpenSSL)
	SSH support: no (--with-libssh2)
	zlib support: enabled
	GSS-API support: no (--with-gssapi)
	SPNEGO support: no (--with-spnego)
	TLS-SRP support: no (--enable-tls-srp)
	resolver: default (--enable-ares / --enable-threaded-resolver)
	ipv6 support: enabled
	IDN support: no (--with-{libidn,winidn})
	Build libcurl: Shared=yes, Static=yes
	Built-in manual: enabled
	--libcurl option: enabled (--disable-libcurl-option)
	Verbose errors: enabled (--disable-verbose)
	SSPI support: no (--enable-sspi)
	ca cert bundle: /etc/pki/tls/certs/ca-bundle.crt
	ca cert path: no
	LDAP support: no (--enable-ldap / --with-ldap-lib / --with-lber-lib)
	LDAPS support: no (--enable-ldaps)
	RTSP support: enabled
	RTMP support: no (--with-librtmp)
	metalink support: no (--with-libmetalink)
	HTTP2 support: disabled (--with-nghttp2)
	Protocols: DICT FILE FTP FTPS GOPHER HTTP HTTPS IMAP IMAPS POP3 POP3S RTSP SMTP SMTPS TELNET TFTP
	make && make test && make install

view raw gistfile2.txt hosted with ❤ by GitHub

Then I succeeded to run plenv install-cpanm

% plenv install-cpanm      
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   303    0   303    0     0    509      0 --:--:-- --:--:-- --:--:--  7973
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100  262k  100  262k    0     0   113k      0  0:00:02  0:00:02 --:--:-- 3012k
--> Working on App::cpanminus
Fetching http://www.cpan.org/authors/id/M/MI/MIYAGAWA/App-cpanminus-1.7004.tar.gz ... OK
Configuring App-cpanminus-1.7004 ... OK
Building and testing App-cpanminus-1.7004 ... OK
Successfully installed App-cpanminus-1.7004
1 distribution installed

Facebook::OpenGraph Ver.1.21 supports API versioning

On 2014-04-30 Facebook announced API versioning to improve its stability. Each version is guaranteed to work 2 years so we do not have to be afraid of 90 day breaking change policy anymore. The version we were using prior to this introduction is called version 1.0 while the new version introduced along with API versioning policy is called version 2.0.

Versioned Request

Making versioned request is pretty easy. Just like other major platform APIs, you prepend version number to the end point like below:

/v2.0/me/friends

Unversioned request is also supported. Just don't prepend version number and it's considered "unversioned." The document says "An unversioned call will default to the oldest available version of the API," but here is one tricky part:

For apps that existed before April 30th 2014, making an API call without specifying a version number ('unversioned') is equivalent to making a call to the v1.0 of the API.
For apps created on or after April 30th 2014, making an API call without a specifing a version number is equivalent to making a call to v2.0 of the API.

So when you are making unversioned request, just be careful when the request app was created.

Facebook::OpenGraph 1.21

I implemented versioning support to Facebook::OpenGraph and launched it as Ver. 1.21. This change is backward compatible. If you update module and don't make any change to your code it makes unversioned request, which is exactly the same as previous version of this module.

API Versioning

With this version, you can specify default version on initialization as follows:

my $fb = Facebook::OpenGraph->new(+{
    app_id  => 12345,
    secret  => 'qwerty',
    version => 'v2.0',
});

If you don't specify any version,  version is left undef and each request becomes unversioned request.
You can still set version on each request by specifying versioned path such as /v1.0/me/friends. This will override the version configuration given on initialization.

my $fb = Facebook::OpenGraph->new(+{version => 'v2.0'});
$fb->get('/zuck');      # Use version 2.0 by accessing /v2.0/zuck
$fb->get('/v1.0/zuck'); # Ignore the default version and use version 1.0
 
my $fb = Facebook::OpenGraph->new();
$fb->get('/zuck'); # Unversioned API access since version is not specified
                   # on initialisation or each reqeust.

Dialog Versioning

Facebook Platform also supports dialog versioning. If you specify version -- let's say v2.0 -- on initialization, $fb->auth_uri() will return versioned Login dialog URL like https://www.facebook.com/v2.0/dialog/oauth.

If you have any enhancement idea, bug fix or question. Feel free to add an issue.