| Detailed description |
Would it be possible to make packages available for download as soon as they are successfully built?
It seems to happen quite often that the following situation arises (this happens to my project now and seems to have happened to other projects):
Packages are built successfully both in source form and in binary form for both Windows and Mac, but
the package check fails for some reason not being a bug in the package itself, but an unsatisfied dependency (package depends on another package on Rforge, but not on CRAN, or depends on a newer version than that available on CRAN, see [#2432] ,[#2479] ,[#2497]), or checking fails because of some problem that appears to be related to the build/check system itself (see [#2395],[#2471]).
I am very grateful for having the R-forge platform, because it allows to distribute development versions of packages that are not yet ready for CRAN. But the usefulness of R-forge is a bit diminished if the availability of package downloads is handled in such a restrictive way.
Many thanks!
Best,
Martin |
|
