-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gather informations about dependence libraries version #452
Comments
That's great! It sounds like exactly what we need. Thank you. Do you have any idea when it will be implemented? |
@lizfrank there is no ETA for now, nobody is foreseen to work on it for the moment. |
@kelson42 I would like to work on this can you explain more about the issue. |
#465 make libzim install the |
What is asked in the ticket is not delivered yet. We should keep the ticket open or revamp it. We need a method giving the necessary information, so external software can display them. |
We have a define publicly available. External software can use it to display them. |
I believe we should have a method delivering this list, otherwise each software will have to handle the whole stack of deps on its own. Which is super annoying. |
I don't think that libzim should export version of other libraries. |
If we don't do so, we will have:
@mgautierfr So why would want to do that if a simply abstraction in libzim/libkiwix would provide this in a normalised manner? |
Alternative idea, possibly complementary: version the ZIM file spec. Track somewhere (changelogs) which versions of libzim/zimwriterfs/etc. are compatible with which ZIM spec version. This is done for other file formats, e.g. hdf5, toml, etc. |
With our tools (typically zim-tools and kiwix-tools), we need to know which versions of the libzim/libkiwix/... binary runs against.
Therefore. we should be able to deliver the list of librairies we need with there version used for compilation/linking.
The tools, following a similar procedure with their own deps, should be able to print the information with option
-v
.The text was updated successfully, but these errors were encountered: