Thank you all for your help. I won't set up a repo for gurobi because I don't have the authority to do that. It seems like I should include gurobi in Suggests, even though it cannot be automatically installed from any repository, include instructions for installing it in Description, and just deal with the fact that cmd check will always flag it as a problem. It does seem more convenient to just put it in Enhances so it is not flagged on a check since it is not used in any examples and the code that uses its functions has alternative options.
Noah On Mon, Jun 7, 2021 at 12:30 PM Uwe Ligges <lig...@statistik.tu-dortmund.de> wrote: > > > On 05.06.2021 01:47, Dirk Eddelbuettel wrote: > > > > On 4 June 2021 at 16:21, Balasubramanian Narasimhan wrote: > > | Suggests" would trigger an attempt to install gurobi, which is not on > CRAN. > > > > To my understanding that is not the case. It would only do so if and when > > install.packages() is asked to also install packages in Suggests:. And > point > > of Suggests: is that that is not automagic. > > > > I actually Suggests, together with Additional_Repositories: (for which > Noah > > may have to set the repo up, I have not checked if gurobi has one) may > be the > > correct call. > > That would indeed be ideal. As far as I know there is not CRAN-like repo > with gurobi. Following the CRAN policies you can exolain in the > Description field of the DESCRIPTION file how to get that package to > your users. > > Best, > Uwe Ligges > > > Dirk > > > > ______________________________________________ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel > [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
