Bug 64911 - Check strict version of bundled libs when building against external copies in ./configure
Summary: Check strict version of bundled libs when building against external copies in...
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dev-related
  Show dependency tree / graph
 
Reported: 2013-05-23 11:44 UTC by Björn Michaelsen
Modified: 2024-03-27 08:01 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Michaelsen 2013-05-23 11:44:17 UTC 
Our bundled libs, which come with an external copy (e.g. liborcus, libwp*) are wildly untested when not build with the same version as the bundled copy, see for example:
http://nabble.documentfoundation.org/Fwd-libreoffice-liborcus-build-problem-td4056820.html

./configure should strictly check the versions that a LibreOffice release will work with. IMHO it is better to be too strict than too liberal (that is accepting external versions that accidentally work), as everything else results is huge additional workload for the QA.

So for example liborcus should be checked to be libocrus-0.4 for LibreOffice 4.0.x and libocrus-0.6 for LibreOffice 4.1.x/master.
Comment 1 Björn Michaelsen 2013-10-04 18:47:56 UTC 
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.

see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Comment 2 Robinson Tryon (qubit) 2015-12-14 06:50:28 UTC Comment hidden (obsolete)
Comment 3 Robinson Tryon (qubit) 2016-02-18 14:52:34 UTC Comment hidden (obsolete)
Comment 4 Yahia Ayman Ahmad 2024-02-23 12:54:15 UTC 
Working on this bug
Comment 5 Buovjaga 2024-02-23 14:46:39 UTC 
(In reply to Yahia Ayman Ahmad from comment #4)
> Working on this bug

Please wait: it could be that this should not be implemented after all. This easy hack was filed over 10 years ago and has not been reviewed since.
Comment 6 Buovjaga 2024-02-23 19:47:07 UTC 
Closing per discussion in dev chat. Summary:

not seen as necessary/it would be a pain for distro packagers if it wouldn't fit their version/the check cannot be an exact version but must be an "at least" in any case. And that will conflict with LTS distros that rather backport patches/secfixes than using the new upstream version.