So the Bower registry is no longer accepting new package registrations:
? Registering a package will make it installable via the registry (https://registry.bower.io), continue? Yes bower register git://github.com/jordanmartinez/purescript-interpolate.git bower EUNKNOWN Unknown error: 500 - Registering bower package names is not supported anymore. You can install any bower package on github with command like "bower install jquery/jquery-dist --save" * ERROR: Subcommand terminated with exit code 1
The impression I have is that most PureScript users aren’t heavily depending on Bower these days anyway, but using Spago instead. Also, this isn’t an immediate issue for people consuming packages via Bower, as installation still seems to be working fine.
However, this change does have implications for Pursuit and package-sets. The Pursuit package publishing guide, and the
pulp publish flow, both assume that you are publishing your package to Bower before publishing it to Pursuit. (The main reason we have asked package authors to do this is that it ensures that package names are unique, i.e. it should prevent two different authors both thinking they own a certain package name.) The
purescript/package-sets repo has a similar policy:
All packages that are included here must first be published via
bowerwith no exceptions. Since there are two distribution methods for packages (the Bower registry and the package sets), we rely on the Bower registry to act as a “central registry of package names” for both methods. This prevents divergence in the ecosystem - e.g. having two different codebases for a package called “prelude”.
We’ll need to come up with a new policy for both of these, and more generally work out what the implications are for packaging in PureScript going forward, so I’m designating this thread for this purpose. There’s some related discussion in the thread Blogged: thoughts on PureScript package management too which might be useful as background.