[Libreoffice-bugs] [Bug 53894] New: Fix external ICU version check

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=53894

             Bug #: 53894
           Summary: Fix external ICU version check
    Classification: Unclassified
           Product: LibreOffice
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: medium
         Component: Libreoffice
        AssignedTo: libreoffice-bugs at lists.freedesktop.org
        ReportedBy: jkim at FreeBSD.org


Created attachment 65913
  --> https://bugs.freedesktop.org/attachment.cgi?id=65913
Fix ICU version check.

ICU changed the versioning scheme since 49 but it is not reflected in the
configure script.

http://userguide.icu-project.org/design

- ICU Release Version Number (ICU 49 and later)

The first version number field contains the ICU release version number, for
example 49. Each new version might contain new features, new locale data, and
modified behavior. (See below for more information on ICU Binary Compatibility
(§).)

The second field is 1 for the initial release (e.g., 49.1). The second and
sometimes third fields are incremented for binary compatible maintenance
releases.

    For maintenance releases for only either C or J, the third field is
incremented (e.g., ICU4C 49.1.1).
    For shared updates for C & J, the second field is incremented to 2 and
higher (e.g., ICU4C & ICU4J 49.2).

(The second field is 0 during development, with milestone numbers in the third
field during that time. For example, 49.0.1 for 49 milestone 1.)

- ICU Release Version Number (ICU 1.4 to ICU 4.8)

In earlier releases, the first two version fields together indicated the ICU
release, for example 4.8. The third field was 0 for the initial release, and 1
and higher for binary compatible (bug fixes only) maintenance releases (e.g.,
4.8.1). The fourth field was used for updates specific to only one of Java,
C++, or ICU-in-Eclipse.

The second version field was even for formal releases ("reference releases")
(e.g., 1.6 or 4.8) and odd during their development (unreleased unstable
snapshot versions; e.g., 4.7). During development, the third field contained
the milestone number (e.g., 4.7.1 for 4.8 milestone 1). For very old ICU code,
we published semi-formal “enhancement” releases with odd second-field numbers
(e.g., 1.7).

Library filenames and some other internal uses already used a concatenation of
the first two fields ("48" for 4.8).

Note this change is purely cosmetic because 49 is much bigger than 5, of
course. ;-)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.