general question: dependency versioning #18
Description
Dependency hell is going on ....while not an issue now this clould be problematic in the future as kwb.utils is a dependency of kwb.file:
https://github.com/KWB-R/kwb.file/blob/fa857fa693825216d6334817f66b9a5ce645175e/DESCRIPTION#L33
while kwb.nextcloud pins to:
Line 34 in 6a26f78
What remotes is doing on my computer is this:
remotes::install_github("kwb-r/kwb.nextcloud@dev")
Using github PAT from envvar GITHUB_PAT
Downloading GitHub repo kwb-r/kwb.nextcloud@dev
Downloading GitHub repo kwb-r/kwb.file@v0.3.0
Downloading GitHub repo kwb-r/kwb.utils@master
Running `R CMD build`...
* checking for file 'C:\Users\micha\AppData\Local\Temp\RtmpwXWz2t\remotes69ac700c721e\KWB-R-kwb.utils-fe0a495/DESCRIPTION' ... OK
* preparing 'kwb.utils':
* checking DESCRIPTION meta-information ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* building 'kwb.utils_0.6.0.tar.gz'
Installing package into ‘C:/Users/micha/Documents/R/win-library/4.0’
(as ‘lib’ is unspecified)
So version pinning in one package fails if it references another package with a diverging verion. I have no clue how to handle such things sustainable. This issue is not limited to kwb.nextcloud but to all R packages with reverse dependencies.