Barry deFreese wrote: > The short description for libzlcore is not very informative and I > believe also not policy compliant. Not very informative, agreed. Does "ZLibrary cross-platform development library (development files)" sound better for you (and similar short descriptions for other ZLibrary binary packages)?
> Perhaps: "cross platform development library" or > something similar? That is probably too generic. > > The long description is also not exactly clear on what particular > functionality this library provides. Fully agreed. I have situation, that ZLibrary is used only by fbreader and it is the main part of it. Author doesn't provide any public info about this library - it is only semi-self-independent part of fbreader code and functionality. And I, as user of fbreader and maintainer of the package, does not actually know exact functionality provided by this library - it just makes fbreader working. Is it bad approach in this case? Should I make a detailed look into library's public interfaces and build some more descriptive? -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.
signature.asc
Description: OpenPGP digital signature
