[User feedback] Provide more clear guidance on installation in Readme

[kumamiao]

• teal.reporter update README teal.reporter#102 and Update installation instructions teal.reporter#109
• teal.logger update readme teal.logger#24 and update installation instructions teal.logger#25
• teal.widgets update installation instructions teal.widgets#64
• teal.slice README and DESCRIPTION teal.slice#66
• teal.data update readme teal.data#79 and then update installation instructions teal.data#83
• teal.transform DESC and README teal.transform#80
• teal.code DESC and README teal.code#50
• teal DESC and README #684
• tmg DESC and README teal.modules.general#425
• tmc DESC and README teal.modules.clinical#531
• osprey update installation instructions osprey#89
• teal.osprey README and DESC teal.osprey#159
• goshawk update installation instructions goshawk#162
• teal.goshawk DESC and README teal.goshawk#166
• tmh - is hermes on bioconductor now? readme and desc teal.modules.hermes#262
• scda readme and desc scda#88
• scda.2021 README scda.2021#83
• scda.2022 readme scda.2022#55
• tern update installation instructions tern#629
• tern.mmrm readme tern.mmrm#88
• tern.rbmi (note not in last release) 668 install@main tern.rbmi#34
• nestcolor ((note not in last release) updating installation instructions nestcolor#13

---

@wangh107

By directly following the installation in the Readme page, installing teal would give the following error:
ERROR: dependencies ‘teal.data’, ‘teal.logger’, ‘teal.widgets’ are not available for package ‘teal.slice’

This issue: it would be good to add some notes about dependencies like in teal.slice Readme

For future, wondering if we could start to think if users could install nest as a whole like tidyverse

[nikolas-burkoff]

We could add in:

You might need to manually install all of the package dependencies before installing this package as without the dependencies = FALSE argument to install_github it may produce an error.

As this is shown in (hopefully) all the other repos with NEST dependencies

Or we could use this issue to sort out the easiest way to install packages... @kumamiao @dinakar29

[kpagacz]

I see our READMEs suggest this:

The problem here is dependencies = FALSE (thankfully missing from the teal README). For now, as we do not have any public repository for our packages that causes these problems.

@dinakar29 is working asap to put our packages somewhere public. Depending on how long it takes, we might want to think about changing the DESCRIPTION files to point to our public github repos as a dependency so users can get a working installation.

[gogonzo]

Please check if including Remotes information in the description can help also. Please use remotes instead of devtools

[cicdguy]

Adding Remotes will help publish to https://pharmaverse.r-universe.dev/ui#packages
This can host the most recent version of packages. Packages are built every 60 minutes and published there.

[cicdguy]

We also had a discussion today, as a long term goal, to publish all public Github NEST packages to CRAN. More on that soon.
June release is available here publicly: https://github.com/insightsengineering/depository, but not a sustainable solution.