>       This case proposes the most recent stable release of LibIDN,
>       0.6.8.
>
>       This case seeks Micro/Patch Relase Binding.
>
> 2.    Technical issues
>
>       2.1.    Key objects.
>
>       /usr/bin/idn
>
>       /usr/lib/libidn.so.11.5.22
>       /usr/lib/libidn.so.11 -> libidn.so.11.5.22
>       /usr/lib/libidn.so -> libidn.so.11.5.22
>   
Interesting that the release number and the library versioning numbers 
don't agree.

Can you explain this?

Insert broken record comment about number of appropriate digits on 
library versions.

(Bart - see if you can convince Rod to come to any discussion about 
this.  It might help.)
>       /usr/include/idn/stringprep.h
>       /usr/include/idn/idna.h
>       /usr/include/idn/punycode.h
>       /usr/include/idn/idn-free.h
>       /usr/include/idn/pr29.h
>       /usr/include/idn/tld.h
>       /usr/include/idn/idn-int.h
>
>       /usr/share/lib/java/libidn-0.6.8.jar
>
>       /usr/share/man/man1/idn.1
>       /usr/share/man/man3/idna_strerror.3
>       /usr/share/man/man3/idna_to_ascii_4i.3
>       /usr/share/man/man3/idna_to_ascii_4z.3
>       /usr/share/man/man3/idna_to_ascii_8z.3
>       /usr/share/man/man3/idna_to_ascii_lz.3
>       /usr/share/man/man3/idna_to_unicode_44i.3
>       /usr/share/man/man3/idna_to_unicode_4z4z.3
>       /usr/share/man/man3/idna_to_unicode_8z4z.3
>       /usr/share/man/man3/idna_to_unicode_8z8z.3
>       /usr/share/man/man3/idna_to_unicode_8zlz.3
>       /usr/share/man/man3/idna_to_unicode_lzlz.3
>       /usr/share/man/man3/pr29_4.3
>       /usr/share/man/man3/pr29_4z.3
>       /usr/share/man/man3/pr29_8z.3
>       /usr/share/man/man3/pr29_strerror.3
>       /usr/share/man/man3/punycode_decode.3
>       /usr/share/man/man3/punycode_encode.3
>       /usr/share/man/man3/punycode_strerror.3
>       /usr/share/man/man3/stringprep.3
>       /usr/share/man/man3/stringprep_4i.3
>       /usr/share/man/man3/stringprep_4zi.3
>       /usr/share/man/man3/stringprep_check_version.3
>       /usr/share/man/man3/stringprep_convert.3
>       /usr/share/man/man3/stringprep_locale_charset.3
>       /usr/share/man/man3/stringprep_locale_to_utf8.3
>       /usr/share/man/man3/stringprep_profile.3
>       /usr/share/man/man3/stringprep_strerror.3
>       /usr/share/man/man3/stringprep_ucs4_nfkc_normalize.3
>       /usr/share/man/man3/stringprep_ucs4_to_utf8.3
>       /usr/share/man/man3/stringprep_unichar_to_utf8.3
>       /usr/share/man/man3/stringprep_utf8_nfkc_normalize.3
>       /usr/share/man/man3/stringprep_utf8_to_locale.3
>       /usr/share/man/man3/stringprep_utf8_to_ucs4.3
>       /usr/share/man/man3/stringprep_utf8_to_unichar.3
>       /usr/share/man/man3/tld_check_4.3
>       /usr/share/man/man3/tld_check_4t.3
>       /usr/share/man/man3/tld_check_4tz.3
>       /usr/share/man/man3/tld_check_4z.3
>       /usr/share/man/man3/tld_check_8z.3
>       /usr/share/man/man3/tld_check_lz.3
>       /usr/share/man/man3/tld_default_table.3
>       /usr/share/man/man3/tld_get_4.3
>       /usr/share/man/man3/tld_get_4z.3
>       /usr/share/man/man3/tld_get_table.3
>       /usr/share/man/man3/tld_get_z.3
>       /usr/share/man/man3/tld_strerror.3
>   
Ditto broken record comment about man page directory.

In this case, there should also probably be some form of entry in the 
interface table.
>       2.3.    Language bindings
>
>       LibIDN is written in C. Language bindings for Java are included.
>   
Where are the Java language bindings defined an documented.
>       3.3.    Exported interfaces
>
>       NAME                    STABILITY               NOTES
>
>       SUNWgnu-idn             Uncommitted             Package name
>
>       /usr/bin/idn            Uncommitted             Executable location
>       /usr/lib/libidn.so.11.5.22      Uncommitted     Library location
>       /usr/lib/libidn.so.11   Uncommitted     Symbolic link
>       /usr/lib/libidn.so      Uncommitted             Symbolic link
>       /usr/share/lib/java/libidn-0.6.8.jar    Uncommitted     JAR file
>   
Humm,... different version number on the jar file.

Do we really want to start down this path of version numbers on the jar 
file?  Particularly this
many digits?  Think about the binding and support issues that entails.

- jek3


Reply via email to