#303 closed task (fixed)
Update DjVuLibre to latest version (3.5.27)
Reported by: | Lewis Rosenthal | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.4.0 |
Component: | Plugin: DjVu | Version: | 1.3.6 |
Keywords: | Cc: |
Description
While certainly not a priority, we may get some better rendering of DjVu files with a newer DjVuLibre.
Change History (8)
comment:1 by , 8 years ago
comment:3 by , 8 years ago
Doesn't this just complicate our dependency problem? Does this have an interface that avoids breaking the lucide plugin every time the lib is updated? If this will force a rebuild how will you keep lucide in sync on users machines? I think this would force us to split the plugins when updating as you will have individuals who don't want to update poppler but do want to update DjVu or some such combination. If we introduce new plugins the problem will just grow worse.
Is there a way with yum/rpm to install a plugin in the lucide directory (ie using an environment variable)? Can it use the presence of this variable to identify the dependency? If so and we can't find a solution to rebuilding, we could just package the plugins and update the lucide install with the new plugin when the lib is updated. We could redesign the warpin so when updating lucide installing each plugin is optional so if someone doesn't want to install the latest lib they simply keep their old plugin. The warpin would add the environment variable on initial install or on update from 1.3.5 or older. This would mean building the plugins against at least some older versions of the libs to prevent lucide from being broken if someone back levels the lib.
comment:5 by , 8 years ago
I doubt it makes things complicated, at least not for djvulibre. As this api is stable and not much changes in this regard anyway. Btw rpm version is available now. The rpm version brings a dll name change, as we build it now with our normal toolkit.
comment:6 by , 8 years ago
djvulibre is now in rpm and I have built with it and jpeg (related to #305) successfully. The changes are trivial to do the build.
comment:7 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks for the plugin update, Andy!
comment:8 by , 6 years ago
Milestone: | Future → 1.4.0 |
---|
Move closed tickets to completed milestone. Many of these were completed before 1.4.0
please also here use the not yet releases rpm version. Version 3.5.25 is in the ports repo since several month/years. a rpm version is planned since longer