-
Notifications
You must be signed in to change notification settings - Fork 758
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
Build vignettes in install() #1578
Comments
Looking into this, is there an idea as to how to change default behavior of
Do I have that logic correct? Would we want |
@hadley was saying to build vignettes with the Now that remotes has support for building packages this should be a matter of calling the remotes functions with I am somewhat undecided if this is worth doing now, it will make maintenance more of a burden. |
So it's clear to me that if I have a package on github (not yet on CRAN), and used However, this prevents me from displaying my vignette on github per se. The vignette is (kind of by definition) the best way to explain how to use my package and would like to be able to display it to prospective downloaders on github itself. So I have 2 questions:
|
@DataStrategist If you want to display live vignettes, the best solution (IMO) is pkgdown. You are welcome to try something else based on not ignoring |
@hadley So I guess the question (and this is def. a soft question) then becomes "what's the difference between walthroughing your package in |
@DataStrategist pkgdown turns your vignettes into a website |
@hadley so it does. I'm going to go into the corner and curl into a ball and cry myself to sleep now... thanks. |
I think we're now unlikely to do this, or if we do, it'll be as a general re-thinking of how we handle vignettes. |
This should be the default behaviour, once the package installation code has moved to remotes. That way remotes focusses on fast installation and devtools on more accurate simulation of install from CRAN.
The text was updated successfully, but these errors were encountered: