Sorry for any lack of knowledge, I have not been the best at keeping up on this thread.

Does this mean you actually did keep zlibrarry in user/*? I'm concerned of spreading issues related to it to something that should be for packages people consider ready for Extras

Some personal philosophy: People having issues in extras-devel is fine, its expected, if you don't want it, stay out. Bringing those issues into extras-testing is bad I think because it should reflect what things should be like in extras (if it was deemed ready immediately and promoted, not that issues shouldn't be left to be found in the QA process) which is bad.

More philosophy: an end-user should not be seeing libraries in Extras. This is going to be enabled by default so anyone and everyone will see "zlibrary" as an installation option. What?

I forgot, what is wrong with the solution of packaging zlibrary inside of fbreader rather than separately? is it really gaining an advantage by being a separate library? Even if one other component depends on it, is the amount of advantage of sharing zlibrary's really outweigh the headache of this?