icu

[Jason W]

Thanks to Roberto A. Foglietta we have icu:

Code: [Select]

Title:          icu.tcz
Description:    International Components for Unicode (TESTING)
Version:        4.0.1
Author:         various
Original-site:  http://site.icu-project.org/
Copying-policy: ICU License
Size: 8172K
Extension_by:   Roberto A. Foglietta
Comments:       ICU is a mature, widely used set of C/C++
and  Java libraries providing Unicode and
Globalization support for software applications.
ICU is widely portable and gives applications
the same results on all platforms and between
C/C++ and Java software.
Change-log:     2009/04/28 First version
Current:    2009/04/28 First version



[Jason W]

THanks to Arslan S. for:

Code: [Select]

Title:          icu-dev.tcz
Description:    International Components for Unicode, development files.
Version:        4.4
Author:         various
Original-site:  http://site.icu-project.org/
Copying-policy: ICU License
Size: 1M
Extension_by:   Roberto A. Foglietta, Arslan S.
Comments:       ICU is a mature, widely used set of C/C++
and  Java libraries providing Unicode and
Globalization support for software applications.
ICU is widely portable and gives applications
the same results on all platforms and between
C/C++ and Java software.
Change-log:     2009/04/28 First Version 4.0.1 by Roberto A. Foglietta
Current:    2010/04/29 Updated to 4.4 & splitted devs (Arslan S.)



Code: [Select]

Title:          icu-doc.tcz
Description:    International Components for Unicode, documentation files.
Version:        4.4
Author:         various
Original-site:  http://site.icu-project.org/
Copying-policy: ICU License
Size: 28K
Extension_by:   Roberto A. Foglietta, Arslan S.
Comments:       ICU is a mature, widely used set of C/C++
and  Java libraries providing Unicode and
Globalization support for software applications.
ICU is widely portable and gives applications
the same results on all platforms and between
C/C++ and Java software.
Change-log:     2009/04/28 First Version 4.0.1 by Roberto A. Foglietta
Current:    2010/04/29 Updated to 4.4 & splitted devs (Arslan S.)



Code: [Select]

Title:          icu.tcz
Description:    International Components for Unicode.
Version:        4.4
Author:         various
Original-site:  http://site.icu-project.org/
Copying-policy: ICU License
Size: 7.6M
Extension_by:   Roberto A. Foglietta, Arslan S.
Comments:       ICU is a mature, widely used set of C/C++
and  Java libraries providing Unicode and
Globalization support for software applications.
ICU is widely portable and gives applications
the same results on all platforms and between
C/C++ and Java software.
Change-log:     2009/04/28 First Version 4.0.1 by Roberto A. Foglietta
Current:    2010/04/29 Updated to 4.4 & splitted devs (Arslan S.)



[Arslan S.]

icu.tcz has md5sum error

edit: hmm for some reason for the first time i got checksum error but now it is ok

[maro]

BTW, I believe a bit of a problem has come up due to the version change.

[Arslan S.]

the reason why i have updated icu because i have compiled openoffice3

i will rebuild webkit soon

[^thehatsrule^]

It's probably a good idea to rollback this extension and that future packages should all contain version numbers (ie icu-4.0.tcz, icu-4.4.tcz) due to its incompatible changes.

[Arslan S.]

It's probably a good idea to rollback this extension and that future packages should all contain version numbers (ie icu-4.0.tcz, icu-4.4.tcz) due to its incompatible changes.

sure this could be done, but a better idea is to keep current and latest version as icu.tcz

[^thehatsrule^]

That will probably just create future problems, i.e. for version 4.6.  If there's no further reasons, a rollback will be queued in.

[Jason W]

Probably best to coordinate an upgrade of icu with a rebuild of it's dependent extensions so they can be updated at once rather than causing breakage.  Kind of like with Python.

[^thehatsrule^]

Both now are now available as icu-40 and icu-44.  Corresponding .dep files were adjusted.  Please report any problems.

[maro]

Was that really necessary to create two versions of the icu extension when only 'sword.tcz' (and 'sword-dev.tcz') still depend on the old one? Why not re-build the one "offending" extension, which appears to be only required by 'bibletime.tcz' anyway.

Or have I missed out on an important technical reason to keep two versions around? I thought the idea was not to maintain multiple versions of the same thing unless there might be really good reasons for this (e.g. 'python-2.5.2.tcz' in addition to 'python.tcz').

BTW, 'icu-44-dev.tcz.dep' still lists 'icu.tcz' as it's only dependency.

[^thehatsrule^]

Yea, releases don't seem to be compatible.  Also fixed that dep, thanks.

[maro]

So what is the upshot? Are we now stuck with having two versions of a library because some old and probably extremely seldom used extension has not been re-build?

I'm raising this because I'm getting worried that this is the start of a "slippery slope" where TC ends up with a "mess" of various versions of the same thing just because no one cared. I thought the aim was to avoid multiple versions and stay reasonably current with just a single library version. I guess the "pain" involved now to fix this is small compared to the pain at a later point in time when things have become really messy.

[^thehatsrule^]

I don't know how popular, etc. this library is, but the main reason is compatibility.  Having multiple versions where some thing such as the API differs allows for 'older' extensions to (still) work, users may have their own stuff that require or already using a certain version, etc.  New (major) versions are likely to revisit the same problem.  Plus, at least in this case, maintenance is likely to be low.  Similar situations could include Python, Java, X, etc.  I think the gains outweigh the fallacy