From bart.smaalders@sun.com Tue Mar 20 21:07:07 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2L477GJ016385 for ; Tue, 20 Mar 2007 21:07:07 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2L473SW029448 for <@sunmail2sca.sfbay.sun.com:PSARC-EXT@Sun.COM>; Wed, 21 Mar 2007 04:07:06 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF800B01JFSDA00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Tue, 20 Mar 2007 21:07:04 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF800MEKJFSWEF0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Tue, 20 Mar 2007 21:07:04 -0700 (PDT) Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2L473NF003553; Tue, 20 Mar 2007 21:07:03 -0700 (PDT) Received: from [129.146.228.109] (cyber [129.146.228.109]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with ESMTP id l2L473QN029535; Tue, 20 Mar 2007 21:07:03 -0700 (PDT) Date: Tue, 20 Mar 2007 21:06:12 -0700 From: Bart Smaalders Subject: PSARC/2007/167 Including IDN with Solaris To: PSARC-EXT@sun.com Cc: Stefan Teleman Message-id: <4600AF34.5040805@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_2q0YewuHk/B2ehxKfcj8BQ)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0b2 (X11/20070227) Status: RO Content-Length: 9479 This is a multi-part message in MIME format. --Boundary_(ID_2q0YewuHk/B2ehxKfcj8BQ) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT I'm sponsoring the attached fast-track for Stefan Teleman. The requested binding is patch/micro release, and the stability levels are as noted in the document. Materials are in the case directory. This case times out on 3/28/2007. - Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts --Boundary_(ID_2q0YewuHk/B2ehxKfcj8BQ) Content-type: text/plain; name=IDNFastTrack.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=IDNFastTrack.txt Including IDN with Solaris Stefan Teleman 15 March 2007 1. Summary and motivation The inclusion of PHP5 in Solaris has identified a number of missing capabilities. One of these capabilities is a generic implementation of the Stringprep, Punycode and IDNA specifications as defined by IETF Internationalized Domain Names (IDN) Working Group. LibIDN provides such an implementation in a portable and platform-independent manner. According to the IDN web page at GNU.org, LibIDN is known to run on over 20 UNIX-like platforms. This FastTrack case proposes the integration of LibIDN in Solaris. LibIDN is GNU Software [http://www.gnu.org/software/libidn/] [1] and is developed outside of SMI. As such, the SFW Consolidation is the natural choice for LibIDN. 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 /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 LibIDN's functionality is provided by one executable [idn], and one shared library [libidn.so.*]. Key aspects of the facilities provided by LibIDN are discussed below. 2.2 Specifications LibIDN implements the Stringprep, Punycode and IDNA specifications. The Stringprep specification is defined by RFC 3454 [http://www.ietf.org/rfc/rfc3454.txt] [5]. According to the specification, Stringprep "specifies a framework of processing rules for Unicode text. Other protocols can create profiles of these rules; these profiles will allow users to enter internationalized text strings in applications and have the highest chance of getting the content of the strings correct.". In other words, in and of itself, Stringprep is merely a foundation library for Unicode character conversion and representation. It does not implement any protocols. Custom "profiles" implementing formalized protocols can be constructed on top of, and pursuant to, the Stringprep specification. The Nameprep Internet Protocol specification is defined by RFC 3491 [http://www.ietf.org/rfc/rfc3491.txt] [6]. Nameprep specifies the processing rules which allow user input of internationalized domain names (IDNs) into applications, providing the highest success rate of correct string conversion. Nameprep is a Stringprep Profile. The Nameprep processing rules are intended solely for internationalized domain names, and not suitable for, nor do they support, arbitrary text. The Nameprep profile defines the following capabilities (as required by Stringprep): Internationalized Domain Names [IDN] Character universe that represents the possible input and output to Stringprep: Unicode 3.2 [http://www.unicode.org/reports/tr28/tr28-3.html] [4] Other profiles exist for Stringprep: Internet Small Computer Systems Interface [iSCSI] Names, [http://www.ietf.org/rfc/rfc3722.txt] [RFC 3722] [7] Extensible Messaging and Presence Protocol [XMPP] Core, [http://www.ietf.org/rfc/rfc3920.txt] [RFC 3920] [8] Stringprep Profile for User Names and Passwords [SASL], [http://www.ietf.org/rfc/rfc4013.txt] [RFC 4013] [9] None of the profiles enumerated above pertain directly to LibIDN, and, for the purposes of this document, will not be discussed further. The Punycode Specification is defined by RFC 3492 [http://www.ietf.org/rfc/rfc3492.txt] [10]. Punycode specifies an Internet Standard for implementing a "simple and efficient transfer encoding syntax designed for use with Internationalized Domain Names in Applications [IDNA]". Simply put, Punycode tranforms a Unicode string into an ASCII string. The conversion operation is reversible and bidirectional. Unicode characters which can be represented as ASCII are represented literally, and non-ASCII convertible characters are converted to, and represented by, ASCII characters allowed in host name labels [letters, digits, and hyphens]. The IDNA Specification is defined by RFC 3490 [http://www.ietf.org/rfc/rfc3490.txt] [11]. IDNA formalizes a Standard for Internationalized Domain Names [IDNs], and a mechanism named Internationalizing Domain Names in Applications [IDNA] for handling IDNs in a standard manner. IDNs can use characters available in the Unicode Universe. IDNA allows the non-ASCII characters to be represented using only the ASCII character set allowed in host name labels. This backward-compatible conversion and representation is required by existing protocols like DNS. This way, IDNs can be introduced with no changes to the existing infrastructure. IDNA is meant solely for processing domain names, and is not suitable for, nor does it support, free text. 2.3. Language bindings LibIDN is written in C. Language bindings for Java are included. 2.4. Documentation LibIDN provides an extensive and detailed set of man pages for all its interfaces. These manual pages will be installed in the default Solaris manual page location. Additionally, detailed documentation of LibIDN's APIs is provided in HTML format. 3. Interfaces 3.1. Interface Stability LibIDN is an Open Source project, and is controlled by a group of developers external to SMI [GNU/FSF/Simon Joseffson]. Although LibIDN strives to maintain ABI and API compatibility between releases, no explicit guarantees of backwards compatibility between releases are offered by LibIDN's developers. 3.2. Imported interfaces LibIDN imports Standard C Library interfaces, Socket [-lsocket], and Network Services Library [-lnsl] interfaces. NAME STABILITY NOTES Java [for Java bindings] Stable PSARC/2003/696 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 /usr/include/idn/ Uncommitted Include files 4. References [1] http://www.gnu.org/software/libidn/ [2] http://www.gnu.org/software/libidn/manual/libidn.html [3] http://www.gnu.org/software/libidn/reference/ [4] http://www.unicode.org/reports/tr28/tr28-3.html [5] http://www.ietf.org/rfc/rfc3454.txt [6] http://www.ietf.org/rfc/rfc3491.txt [7] http://www.ietf.org/rfc/rfc3722.txt [8] http://www.ietf.org/rfc/rfc3920.txt [9] http://www.ietf.org/rfc/rfc4013.txt [10] http://www.ietf.org/rfc/rfc3492.txt [11] http://www.ietf.org/rfc/rfc3490.txt --Boundary_(ID_2q0YewuHk/B2ehxKfcj8BQ)-- From carlsonj@phorcys.east.sun.com Wed Mar 21 05:23:38 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LCNbfp023685 for ; Wed, 21 Mar 2007 05:23:37 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LCNCY6017574; Wed, 21 Mar 2007 12:23:35 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900C096FAC800@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 05:23:34 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900KV66F90NE0@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 05:23:34 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.0+Sun/8.14.0) with ESMTP id l2LCNXl9008802; Wed, 21 Mar 2007 08:23:33 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.0+Sun/8.14.0/Submit) id l2LCNXKq008799; Wed, 21 Mar 2007 08:23:33 -0400 (EDT) Date: Wed, 21 Mar 2007 08:23:32 -0400 From: James Carlson Subject: Re: PSARC/2007/167 Including IDN with Solaris In-reply-to: <4600AF34.5040805@Sun.COM> To: Bart Smaalders Cc: PSARC-EXT@sun.com, Stefan Teleman Message-id: <17921.9156.731520.775507@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF34.5040805@Sun.COM> Status: RO Content-Length: 639 Bart Smaalders writes: > This FastTrack case proposes the integration of LibIDN in Solaris. > LibIDN is GNU Software [http://www.gnu.org/software/libidn/] [1] > and is developed outside of SMI. As such, the SFW Consolidation is > the natural choice for LibIDN. One really tiny nit: it looks like this is the anticipated follow-on case for 2003/467 "IDN support - OS utilities," and should reference that case. -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From jek3@sun.com Wed Mar 21 14:29:41 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LLTfIV009402 for ; Wed, 21 Mar 2007 14:29:41 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LLTe5d029129; Wed, 21 Mar 2007 14:29:40 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900K0LVPGTR00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 14:29:40 -0700 (PDT) Received: from jurassic-x4600.Eng.Sun.COM ([129.146.17.59]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900APVVPFGX40@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 14:29:39 -0700 (PDT) Received: from [129.150.12.53] (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53]) by jurassic-x4600.Eng.Sun.COM (8.14.0+Sun/8.14.0) with ESMTP id l2LLTbgx414832; Wed, 21 Mar 2007 14:29:38 -0700 (PDT) Date: Wed, 21 Mar 2007 11:29:32 -1000 From: Joseph Kowalski Subject: Re: PSARC/2007/167 Including IDN with Solaris In-reply-to: <4600AF34.5040805@Sun.COM> To: Bart Smaalders Cc: PSARC-EXT@sun.com, Stefan Teleman Message-id: <4601A3BC.8070703@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF34.5040805@Sun.COM> User-Agent: Thunderbird 1.5.0.5 (X11/20060925) Status: RO Content-Length: 3761 > 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 From Stefan.Teleman@sun.com Wed Mar 21 14:56:28 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LLuRfe011045 for ; Wed, 21 Mar 2007 14:56:28 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2LLu7OT029375; Thu, 22 Mar 2007 05:56:24 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900003WY0A000@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 14:56:24 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.108.38]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900AWMWY0GX50@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 14:56:24 -0700 (PDT) Received: from [192.9.61.55] (punchin-client-192-9-61-55.SFBay.Sun.COM [192.9.61.55]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2LLuN5Q394444; Wed, 21 Mar 2007 14:56:23 -0700 (PDT) Date: Wed, 21 Mar 2007 17:55:28 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/167 Including IDN with Solaris In-reply-to: <4601A3BC.8070703@sun.com> To: Joseph Kowalski Cc: Bart Smaalders , PSARC-EXT@sun.com Reply-to: Stefan Teleman Message-id: <4601A9D0.9030206@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF34.5040805@Sun.COM> <4601A3BC.8070703@sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 2353 Joseph Kowalski wrote: > >> 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? Rationally ? No. And this numbering scheme doesn't even follow the so-called "libtool standards". Do I understand what these numbers actually mean ? No, and I seriously doubt anyone else does. I do not see any connection between the distribution version (which is 0.6.8) and the library version. Would I have done this ? No. This is what Simon Josefsson and gnu.org/FSF publish. This is not an unique case. The more FOSS software we integrate into Solaris, the more of these strange numbering schemes we will encounter. For example, MySQL 5.0.33 contains libmysqlclient_r.so.15.0.0 and libndbclient.so.0.0.0. The fundamental problem with changing these numbering schemes to a more rational one is that such a change essentially creates a Solaris fork. > Where are the Java language bindings defined an documented. I will update them in the materials directory. >> 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. Same comments about changing numbering schemes and versions. LibIDN seems to be one of the most fast-changing packages. Between October 2005 and October 2006 there were 8 revisions. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From gww@eng.sun.com Tue Mar 27 15:57:46 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2RMviRl005051 for ; Tue, 27 Mar 2007 15:57:45 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2RMveta012359 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@sun.com>; Wed, 28 Mar 2007 06:57:44 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFL004153S4BS00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 15:57:40 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFL000493S3E040@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 15:57:40 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2RMvdSL013403; Tue, 27 Mar 2007 15:57:39 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2RNv0WC004939; Tue, 27 Mar 2007 15:57:00 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2RNv0SH004938; Tue, 27 Mar 2007 15:57:00 -0800 (PST) Date: Tue, 27 Mar 2007 15:57:00 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/167 Including IDN with Solaris To: PSARC-EXT@sun.com, bart.smaalders@sun.com Cc: Stefan.Teleman@sun.com Message-id: <200703272357.l2RNv0SH004938@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 456 > 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 Again, I believe /usr/lib/64 is also requried. Often it is just assumed. However from other discussions it seem worth ensuring. Gary.. From Stefan.Teleman@sun.com Tue Mar 27 16:05:25 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2RN5OcH005131 for ; Tue, 27 Mar 2007 16:05:25 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2RN5Cit003818; Wed, 28 Mar 2007 00:05:22 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFL00A0344YY700@nwk-avmta-1.sfbay.Sun.COM>; Tue, 27 Mar 2007 16:05:22 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.56.144]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFL00A6G44XB7D0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 27 Mar 2007 16:05:21 -0700 (PDT) Received: from [192.9.61.113] (punchin-client-192-9-61-113.SFBay.Sun.COM [192.9.61.113]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2RN5KBr304368; Tue, 27 Mar 2007 16:05:21 -0700 (PDT) Date: Tue, 27 Mar 2007 18:04:26 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/167 Including IDN with Solaris In-reply-to: <200703272357.l2RNv0SH004938@marduk.eng.sun.com> To: Gary Winiger Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com Reply-to: Stefan Teleman Message-id: <460994EA.1010104@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703272357.l2RNv0SH004938@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 801 Gary Winiger wrote: >> 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 > > Again, I believe /usr/lib/64 is also requried. > Often it is just assumed. However from other discussions > it seem worth ensuring. I will update all the FastTracks with the explicit /usr/lib/64 and /usr/bin/64 paths as well. I'd like to check one detail: are /usr/lib/64 and /usr/bin/64 the preferred paths over /usr/lib/{amd64,sparcv9} and /usr/bin/{amd64,sparcv9} ? --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From gww@eng.sun.com Tue Mar 27 16:25:26 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2RNPQZb005674 for ; Tue, 27 Mar 2007 16:25:26 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2RNPMfN000121 for <@sunmail1brm.central.sun.com:PSARC-EXT@sun.com>; Tue, 27 Mar 2007 16:25:26 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFL00L3352E9Q00@brm-avmta-1.central.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 17:25:26 -0600 (MDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFL00NYT52C1890@brm-avmta-1.central.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 17:25:24 -0600 (MDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2RNPNZG016878; Tue, 27 Mar 2007 16:25:23 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2S0OjxR005007; Tue, 27 Mar 2007 16:24:45 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2S0OjnN005006; Tue, 27 Mar 2007 16:24:45 -0800 (PST) Date: Tue, 27 Mar 2007 16:24:45 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/167 Including IDN with Solaris To: gww@eng.sun.com, Stefan.Teleman@sun.com Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com Message-id: <200703280024.l2S0OjnN005006@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 653 > I will update all the FastTracks with the explicit /usr/lib/64 and /usr/bin/64 > paths as well. Thanks. > > I'd like to check one detail: are /usr/lib/64 and /usr/bin/64 the preferred > paths over /usr/lib/{amd64,sparcv9} and /usr/bin/{amd64,sparcv9} ? I believe if you look at the present /lib and /usr/lib, you'll see a symlink 32 -> ./ and 64 -> / Follow the ON packaging for the paths to put in the packages. I believe so and /usr/lib/isaexec is linked to the name in /usr/bin. Again follow ON packaging. l none usr/bin/=../../usr/lib/isaexec and in proto_ f none usr/bin// 555 root bin Gary.. From bart.smaalders@Sun.COM Fri Mar 30 16:29:44 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2UNTg73022911 for ; Fri, 30 Mar 2007 16:29:44 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2U1OjeQ026651 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@Sun.COM>; Fri, 30 Mar 2007 09:24:46 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFO00B05ZX9AQ00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Thu, 29 Mar 2007 18:24:45 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFO003N3ZX89860@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Thu, 29 Mar 2007 18:24:45 -0700 (PDT) Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2U1OijT023011; Thu, 29 Mar 2007 18:24:44 -0700 (PDT) Received: from [129.146.228.109] (cyber [129.146.228.109]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with ESMTP id l2U1OiQZ018692; Thu, 29 Mar 2007 18:24:44 -0700 (PDT) Date: Thu, 29 Mar 2007 18:23:48 -0700 From: Bart Smaalders Subject: Re: PSARC/2007/167 Including IDN with Solaris To: PSARC-EXT@Sun.COM Cc: Stefan Teleman Message-id: <460C66A4.1050804@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0b2 (X11/20070227) Status: RO Content-Length: 289 An updated copy of the fast track with corrections (case numbers, 64 bit paths, etc) has been placed in the materials subdirectory. This case was approved at yesterday's meeting. - Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts