purescript
Handle package name collisions
Looks like pulp publish will overwrite a previous package by the same name. Happened to me right now when I published https://github.com/jacereda/purescript-benchmark
There was already a package on Pursuit: https://github.com/cyrbon/purescript-benchmark
At the moment we have nothing more than an unverified assumption that people will only try to publish a package with a given name if it is registered in the Bower registry with that name. The only safeguard against this has been that the package publishing guide asks you to publish on Bower before publishing to Pursuit, and this seems to have worked up to now, but obviously it is still fallible since you accidentally did this just now.
I would like to stop this from happening, and the only way I can see of achieving that is to have a slightly tighter integration between Pursuit and a package registry. At the moment that would be Bower, but it could change in the future. I guess we would need to establish not only that the package being published exists, but also that it's the same one as what the registry says, and it's not immediately obvious how to do that...
