While you can put multiple packages in one Git repository, I'd suggest
that you don't do that. Most packages are in their own repository, and
that means that users who want to contribute to your packages are
familiar with that setup. If they have to fork 20 packages at once to
make a contribution to one of them, they are less likely to want to do it.
Duncan Murdoch
On 2024-07-01 6:04 p.m., Kevin R. Coombes wrote:
Hi,
I have been maintaining packages in R-Forge for many tears. Last week I
sent an email to r-fo...@r-project.org to report problems with the build
process. It appears that any changes I have pushed to R-Forge over
approximately the last two months have resulted in the package remaining
in the "Building" state, even though the logs suggest that the package
built successfully on both LINUX and Windows. (Also, four of the six
affected packages only included changes to the man pages to clean up
NOTEs from the R cmd checks on old versions at CRAN, where the new
versions now happily reside.) I have received no response nor
acknowledgement to my email to R-Forge.
Assuming that R-Forge has finally succumbed to the ravages of entropy,
does anyone have advice on creating a git project that contains multiple
R packages? (I really don't want to have to create 20+ new git projects,
one per package).
Best,
Kevin
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
