The main problem is what I wrote in this post: the pod's name is "Sparrow-Framework", and thus any bracketed imports need to be done using that name. Internally, Sparrow always uses a simple "<Sparrow/SP...>".
So I don't know yet if it's possible to keep the pod name (so that people can upgrade easily) and still make the import work.
Would anybody be interested in checking this out?
If that's not possible, we could either change all the imports inside Sparrow, or return to the quotation-mark imports. But if I remember correctly, those didn't work after adding the ".framework" deployment ...