I don't see your problem. You have found a bug in an open source project, i.e. that the package does not work on windows. There are two options to solve this: - Fix the windows issue - Fix the documentation on https://github.com/lindahua/CUDA.jl As you are not the maintainer of this project the best thing to solve this is to report the issue on the CUDA.jl bug tracker and/or provide a PR to fix the issue or fix the documentation. You can just click on README.jl on https://github.com/lindahua/CUDA.jl and change the file which will notify Dahua who would than merge your proposed documentation change.
This is how open source works. Proposing to remove the package from the Pkg manager on the Julia mailing list without reporting an issue on the project page where it belongs to is certainly not the right way to do this. And even when you get no reaction on the mailing list or a bug tracker you should never get angry/frustrated about this. What is if Dahua is on vacation surfing in Hawaii for two weeks. Do you expect him to answer to your messages in that time? There is certainly a point about the quality of packages in the Julia ecosystem. In my opinion the most important thing here is automatic testing on all major platforms, which is if I recall right already available. Maybe it would also be good to have some kind of popularity measure. In this way one could list only the "popular" packages which are in use and not the experimental ones. Am Samstag, 19. April 2014 02:51:47 UTC+2 schrieb Laszlo Hars: > > Tim: We spend too much time on this. I don't believe that telling in the > package home page under what OS the package was tested, and what external > functions are used is too much burden. It should be the norm, but obviously > I am alone with this view. -Laszlo >
