-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[R-package] Remove lgbdl from docs until fix #3035
Conversation
Yeah, I think so! Refer to #2843 (comment). UPD: Or |
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 can confirm that after this PR merged, there are no other mentions of lgbdl
in our repo.
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.
Works for me! I think doc
is appropriate here. We probably broke the integration with lgbdl
a long time ago (its last commit was December 2018) so this PR doesn't represent a breaking change.
@@ -16,7 +16,7 @@ Installation | |||
|
|||
You need to install git and [CMake](https://cmake.org/) first. | |||
|
|||
Note: 32-bit R/Rtools is not supported. | |||
Note: 32-bit (i386) R/Rtools is currently not supported. |
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.
good change!
This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Since the method of installing LightGBM for R changed significantly, using Laurae2/lgbdl package is now broken.
This PR removes lgbdl temporarily from the documentation until a new working replacement package is made (to avoid confusion for end users who attempt using it and see it does not work).
The replacement package is likely to be named differently as there are currently scripts relying on the package pointing to old commits for compatibility.
@StrikerRUS
doc
is this the right label for this PR?