Skip to content
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

cplexAPI package archival #214

Closed
jeffreyhanson opened this issue Nov 12, 2021 · 12 comments
Closed

cplexAPI package archival #214

jeffreyhanson opened this issue Nov 12, 2021 · 12 comments

Comments

@jeffreyhanson
Copy link
Contributor

The cplexAPI R package has been archived on CRAN. Since prioritizr uses this package to interface with CPLEX, this will cause issues for users that rely on CPLEX. I'd reached out to the maintainer of the cplexAPI package, and I'll update this issue once I've heard back from them. In the meantime, the archived version of the cplexAPI package can be installed with:

if (!require(remotes)) install.packages("remotes")
remotes::install_github("cran/cplexAPI")
@ricschuster
Copy link
Member

Thanks Jeff!

@jeffreyhanson
Copy link
Contributor Author

Just to follow up, I emailed the developers of the cplexAPI R package and they've submitted an updated version to CRAN. So, hopefully it should be on CRAN soon.

@jeffreyhanson
Copy link
Contributor Author

@ricschuster, if I remember correctly you mentioned that you were going to scope out Rcplex as a potential replacement, I just wanted to check if you'd had a chance to test it out?

@ricschuster
Copy link
Member

I've tried to install Rcplex on a Windows machine, but haven't been successful so far. No issues on Linux, but will need to spend more time getting this to work on Windows.

@jeffreyhanson
Copy link
Contributor Author

So, I think the plan here is to keep on cplexAPI as a Suggests if possible, and have users install from github.com/cran/cplexAPI - assuming that's ok with CRAN. How does that sound?

@ricschuster
Copy link
Member

Sounds good. Any news from the slack channel in this approach?

@jeffreyhanson
Copy link
Contributor Author

Nah, no one with specific experience to this question has answered (someone chimed in with a guess). I also posted on the publc ROpenSci forums (see https://discuss.ropensci.org/t/optional-suggests-dependency-that-has-been-archived-on-cran/3071), but no one has responded specifcally with a yes/no answer to the specific question. Could you post this question on the R-devel emailing list (https://stat.ethz.ch/mailman/listinfo/r-package-devel)? If so, feel free to use the forum post as a template.

@ricschuster
Copy link
Member

Thanks Jeff. Will post to the R-devel list once I am in (just signed up).

@jeffreyhanson
Copy link
Contributor Author

Brilliant - thank you!

@ricschuster
Copy link
Member

Still haven't gotten on the R-devel list. What do you think about just going ahead without that?

@jeffreyhanson
Copy link
Contributor Author

Yeah, I feel like the CRAN checks would have raised a NOTE or WARNING specifically about archived packages if that's an issue (but could be wrong). Could you take a look at the cran-commands.md in the PR? I added some text about justifying why cplexAPI is included even though its been archived - can you think of any ways to improve it?

@jeffreyhanson
Copy link
Contributor Author

Also, I'm still waiting to hear back from the Matrix developers about 1.5-0 being the version that will be released on the 8th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants