-
Notifications
You must be signed in to change notification settings - Fork 8
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
Organized R Package from Volesti v1.1.2-6 #1
Conversation
@Soumya624 Thanks so much for this commit! The first big step to a brand new repository! |
Hi @TolisChal @vissarion , Thanks for the review. I have added a new commit in this PR with the submodule part. Currently 'src/include' is not there. Those C++ codes are coming through submodule. But, I had to change the header file paths for that. Please have a look. I think 'git pull --recurse-submodules' will work. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I have a few comments inline and a couple below.
- Please remove all binaries from your PR (e.g.
.o
files). - Could you create a README that includes all the instructions needed to build the package? Such as, the submodule related commands.
It returns the following error on my side
|
Hi @vissarion , Thanks for the review and for pointing out this error. I think it's coming due to commit 'a0b26514f96004ac900c5fcb1c49a026443041eb'. I had slightly updated few headers on 'volesti v1.1.2-6' but it wasn't pushed. Updating in the latest PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Soumya624! I verify that the package can be installed and loaded locally.
However, I have a question regarding this commit Soumya624/volesti@a86be1f What is the reason of creating relative paths in includes? It is generally a bad practice. See also this PR GeomScale/volesti#244 that tries to fix/canonicalize include paths.
Hi @vissarion , |
This is probably some issue with your path. A quick remark is that in the CRAN directory structure the Also as it is written in CRAN package structure policy all source files that are going to be compiled should be placed in |
Hi @vissarion , Thanks for clarifying. Just a small follow-up. Should I need to update the CRAN directory structure? I can move the |
Yes, please, but keep in mind that only the |
Hi @vissarion , @TolisChal , Added only the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the objective .o
files from src
. Also please remove .Rbuildignore
and .Rhistory
directories.
Other than the above comment the PR is now in good shape. Thanks @Soumya624! @TolisChal are you OK with merging? |
Hi @vissarion , Thanks for the review. Updated the suggested changes. Please take a look! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am OK with merging after addressing a couple of comments mentioned in the comments.
Very good work! All looks good to me, I'm approving it. |
Hi @vissarion , @TolisChal , Thanks for the review. Updated the recently suggested changes. Would be great if you can have a look! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Separated 'volesti' R package for v1.1.2-6 from 'cran_gen/cran_package' folder. And no errors were observed, while it's getting installed via RStudio.