You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Packages taken from github into bootstrap/software as tar.gz contain the whole repository, minus the .git folder, including files listed in .Rbuldignore.
If we assume the source code is there to be installed, not to extend it or run tests, wouldn't it be more economical in space to keep the tar.gz returned by R CMD build?
For FLasher, for example, the current tar,gz created by taf.bootstrap() takes 4.25 Mb, while the built package uses 775Kb.
What would be the reasons to keep the (almost) full repository instead? Could taf.bootstrap at least apply .Rbuildignore?
The text was updated successfully, but these errors were encountered:
This would also be useful for the workflow I am trying to use explained in #37, @arni-magnusson. Is this an option easy to implement given the R tools being used to create the tar.gz in bootstrap/software?
Packages taken from github into bootstrap/software as tar.gz contain the whole repository, minus the .git folder, including files listed in .Rbuldignore.
If we assume the source code is there to be installed, not to extend it or run tests, wouldn't it be more economical in space to keep the tar.gz returned by R CMD build?
For FLasher, for example, the current tar,gz created by taf.bootstrap() takes 4.25 Mb, while the built package uses 775Kb.
What would be the reasons to keep the (almost) full repository instead? Could taf.bootstrap at least apply .Rbuildignore?
The text was updated successfully, but these errors were encountered: