-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the protobuf recipe #3
Conversation
@s-u Anyway we could get this merged and built on CRAN? @eddelbuettel would like to release a new version of |
Actually I don't -- I'd simply prefer for the existing package to build. Several of my packages never built on that esteemed OS, and @s-u did take to kindly to my suggestion of allowing me to disable builds there. But I, as a maintainer, now get punished by CRAN for It really is not ideal. @coatless is kindly offering to build some libraries but we are running into "issues". |
@s-u Any chance this could get merged? Soon (TM)? |
Thanks, committed, tested, deployed. However, there is a bug in
in |
Will fix. Same idiom is used in other places, and Kurt usually reminds me to do it everywhere. Surprised it slipped here for so long. |
Thanks. That may have been the issue before, since we did have protobuf 2.6.1 which should have been compatible. |
Within days, possibly tomorrow. But please do it anyway. Better to disentangle dependencies on any critical path. |
@s-u Can you, by chance, try the version in the GH repo ? That change was made in July, a good two weeks after the most recent release: |
@s-u: Is there something you can do about this one, please? |
This should update the existing
protobuf
as a library for CRAN builds.We're assuming the CRAN build system has
autoconf
,automake
, andlibtool
available./ cc @eddelbuettel