I cannot/will not to help you do this, but there are people out there who disagree with me who put considerable effort into doing this... the search term you would need in order to find them is "monorepo". But please reconsider... the whole point of putting code into separate packages is to isolate their internals to make them less interdependent... putting all of them into a monorepo can lead you to forget that users experience them as distinct units.
On July 1, 2024 3:04:40 PM PDT, "Kevin R. Coombes" <kevin.r.coom...@gmail.com> 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 -- Sent from my phone. Please excuse my brevity. ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
