SCM

[#2432] 'failed to build' when the problem is in missing packages on R/Forge

Date:
2012-12-11 20:05
Priority:
3
State:
Closed
Submitted by:
Brian Peterson (braverock)
Assigned to:
Nobody (None)
Hardware:
All
Operating System:
All
Severity:
blocker
URL:
http://r-forge.r-project.org/R/?group_id=579&add_log=check_x86_64_windows&pkg=Meucci&flavor=patched&
Summary:
'failed to build' when the problem is in missing packages on R/Forge

Detailed description
http://r-forge.r-project.org/R/?group_id=579&add_log=check_x86_64_windows&pkg=Meucci&flavor=patched&type=00install.out

The package *builds* fine, and in my opinion should be available for download.

quadprog is a CRAN package, widely used. It should be available on the R-Forge build environment.

Aside from that, if R-Forge still seeks to be a *development* platform, then I think you need an additional state other than 'failed to build' for 'failed test' or something similar. If the package builds, it should be distributed. It is up to the developers of development packages to decide when and if they should push to CRAN, if ever. R-Forge should just provide development infrastructure. If you won't distribute it, it makes it difficult to test.

Regards,

Brian

Comments:

Message  ↓
Date: 2013-03-22 23:28
Sender: Martin Elff

I second your comment regarding 'failed to build'. I just submitted a feature request, see [#2635].

Best,
Martin

Attached Files:

Changes

Field Old Value Date By
close_dateNone2018-06-15 06:38gstar
status_idOpen2018-06-15 06:38gstar
Thanks to:
Vienna University of Economics and Business Powered By FusionForge