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 iso
Kevin,
R-Forge is still alive but there are problems with the build queue as you
noticed. The problems occurred after R-Forge upgraded to R 4.4.0 - just as
there was a switch in the maintenance team at WU Wien.
The problem is with the Windows build/check tools which work fine when run
manual
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 contribu
I don't know about R-forge, but it's perfectly workable to put
multiple packages within a single repo, with each package in its own
subdirectory. You'll run into some headaches occasionally with (e.g.)
CI machinery that assumes that the head of a git repo is also the
primary package director
Kevin,
I can't speak to whether R-Forge is dead, we migrated our projects to
github a long time ago.
The most straightforward answer for R packages in git repositories is
to use separate git projects. we were even able to import the entire
SVN history and r-forge issue history to github for each
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 t
