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
{{ message }}
This repository has been archived by the owner on May 19, 2021. It is now read-only.
Do you find yourself repeatedly installing or loading the same packages? How about building a meta-package?
The main goal of a meta-package is to install and load other packages (a famous example is the tidyverse package). But also you may use the pkgdown website of a meta-package as a kind of meeting point for all the packages it gathers (e.g. tidyverse; fgeo).
It turns out that building a meta-package is surprisingly simple. The source code of the tidyverse is an excellent template. You could use it to build your own meta-package, or we could generalize it to create a package that creates a meta-package. Is this getting too meta?
:)
The text was updated successfully, but these errors were encountered:
Summary: Building a package to create a meta-package, such as the tidyverse.
maurolepore
changed the title
Building meta-packages (or a tool to do so)
Building meta-packages (e.g. tidyverse) to centralize multiple packages
May 18, 2018
Do you find yourself repeatedly installing or loading the same packages? How about building a meta-package?
The main goal of a meta-package is to install and load other packages (a famous example is the tidyverse package). But also you may use the pkgdown website of a meta-package as a kind of meeting point for all the packages it gathers (e.g. tidyverse; fgeo).
It turns out that building a meta-package is surprisingly simple. The source code of the tidyverse is an excellent template. You could use it to build your own meta-package, or we could generalize it to create a package that creates a meta-package. Is this getting too meta?
:)
The text was updated successfully, but these errors were encountered: