Comments (3)
A way to describe the intent of INTERNAL_PACKAGE::save_as_rds()
: it's just like here::here()
but substituting the conventions of INTERNAL_PACKAGE for here's set of criteria re: the basis for building paths.
All the processing of Sys.info()["nodename"]
and Sys.info()['user']
plays the same role as here (or rprojroot) looking for a DESCRIPTION file, a .git
directory, etc.
from what-they-forgot.
I am not only compliant, I am also very easily tempted...
why not force users to follow the same convention within their home dir?
Users typically have a certain set up of their local system, each organized to their own logic and preferences. Some like it deep, some like it shallow (personally I am a very shallow person). This way each can place the folder where it makes most sense to him or her.
have a helper function in the package that interactively creates a symlink
Thats an interesting thought. So, you mean that package points to the same location on every system, but that on this location the user creates the pointer to the its personal folder? I think in ease of use it would not make much of a difference. Are there other advantages over our approach in your opinion?
A way to describe the intent of INTERNAL_PACKAGE::save_as_rds(): it's just like here::here()
I have not yet used here
so I cannot comment on this.
from what-they-forgot.
have a helper function in the package that interactively creates a symlink
Thats an interesting thought. So, you mean that package points to the same location on every system, but that on this location the user creates the pointer to the its personal folder? I think in ease of use it would not make much of a difference.
Yes, exactly.
Are there other advantages over our approach in your opinion?
I think it's an advantage that you don't have to edit the source of the package each time a team member comes on board or decides to rename a folder. As it stands, your package source actually needs to change if I am user2 and I decide to keep the data in "cuddly_brocolli/fluffy_otter/" instead of "cuddly_brocolli/lively_hamster". Ditto for when user3 and user4 join the team.
from what-they-forgot.
Related Issues (20)
- Advice re: creating user library doesn't quite make sense
- Where did the "don't use homebrew" advice go? HOT 1
- Should system prep verification use `pkgbuild::check_build_tools()`?
- GitHub search examples
- macOS header problem HOT 1
- Definitive to guide to re-installing a package on Windows HOT 7
- link broken HOT 4
- Mention user vs project specific .Renviron in the chapter about startup files?
- chapter 9 :ref devtools instead of remotes
- Chapter 8.4: Example for path expansion
- Move `master` branch to `main` HOT 1
- [WIP] `xcode-select --install` seems to not work anymore
- For “Maintaining R”, would it be worth adding architecture-specific `R_LIBS_USER` paths?
- Mention `base` package Rprofile as a point of interest? HOT 1
- warn against `save`
- mention memoise package in chapter 1.6 - objects that take a long time to create?
- R Startup .Renviron activity
- exercise callout
- update package installation references
- Environment variables
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from what-they-forgot.