Skip to content
Prev 7420 / 15075 Next

Help in creating a MacOSX binary of the mapdata package 2.1-3?

On Aug 30, 2010, at 3:46 AM, Jooil Kim wrote:

            
Of course it does - you can see that form the logs (sort of since you have different OS and different architecture and thus not really relevant to the error). But that is beside the point. The fact that something compiles doesn't meant it works.
If programs crash and there is "no obvious problem with the source" then why do we bother with debugging? If there was an obvious problem then the author would have fixed it, don't you think? It's the non-obvious problems that we call "bugs".

The point of checks is to verify (to some degree) that a program works the way it was designed. That's why a binary of a package failing checks will not get to CRAN as it doesn't work the way it was designed - to protect users from non-obvious failures. Now why that should be a problem "with those that maintain the MacOSX binaries" is entirely beyond me...

Note that the crash is in a call to maps so the issue could be anywhere from mapdata, maps to R...
Sure - with the same result. That's what the nightly builds do: run checks every night if a package fails - one try a night ... 

Cheers,
Simon