Good question. People all like to use committed interfaces for compilers
and libraries, but the community activities decide the stability.
The submitter will probe the community more for the possibility of
changes in each part and then get back.
Frank.
Danek Duvall Wrote:
> On Fri, Jul 04, 20
Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Clutter for OpenSolaris
1.2. Name of Document Author/Supplier:
Author: Chris Wang
1.3 Date of This Document:
Hi, Roland,
This project is targeting to Indiana 2008.11 release, UTF-8 locales have
higher priority than legacy locales, we will gather more
information/feedback to see if we have future plans for legacy locales.
Regarding to the localization of CLI messages, yes, it would be changed
over tim
Hi, Darren,
Please see my reply in-line,
Darren J Moffat ??:
> What is the motivation for having SCIM as well as the already existing
> IIIMF ? Is SCIM the future and IIIMF will be marked as Obsolete and
> eventually removed ?
SCIM (smart common input method) is a more popular input method
fra
Garrett D'Amore writes:
> Sebastien Roy wrote:
> > Indeed. With Clearview UV, libnet would either have to be modified to
> > either use libdlpi, or minimally be modified to open DLPI devices out
> > of /dev/net in order to function with vanity naming. That part, at
> > least, is architectural and
On Tue, 2008-07-01 at 07:51 -0700, Darren Reed wrote:
> My concern is that in future we will ship a libpcap that is based
> on libdlpi and that thus it may work with a different set of interface
> names than does libnet, possibly leading to application failure
> because interface "foo0" works with
Sebastien Roy wrote:
> On Tue, 2008-07-01 at 07:51 -0700, Darren Reed wrote:
>
>> My concern is that in future we will ship a libpcap that is based
>> on libdlpi and that thus it may work with a different set of interface
>> names than does libnet, possibly leading to application failure
>> beca
Yong Sun wrote:
> This project is targeting to Indiana 2008.11 release, UTF-8 locales have
> higher priority than legacy locales,
Right (except stuff like "zh_CN.GB18030" which still should be preferred
over the UTF-8 variant since the matching goverment requires it (and is
very picky about it)) .
[I've dropped the case number from the subject and set Reply-To.]
On Mon, Jul 07, 2008 at 01:48:24PM +0200, Roland Mainz wrote:
> > we will gather more
> > information/feedback to see if we have future plans for legacy locales.
>
> Ok... my main concern is "interoperabilty", e.g. what happens if
Darren J Moffat wrote:
>
> Post this case I expect it will look like this
> ---
>
> Requesting System Maintenance Mode
> SINGLE USER MODE
>
> Enter username (control-d to bypass): darrenm
Implementation suggestion: It would be nice for hitting carriag
I am sponsoring this case for Jedy Wang. The timer has been set to
07/13/2008. The case directory contains this proposal. The project
is requesting the integration of Python Notify, and requesting a
Minor release of Solaris.
Thanks,
Cecilia
Yong Young Sun wrote:
[snip]
> 2. Project Summary
>2.1. Project Description:
> Add the following South East Asia locales support to current
> OpenSolaris.
> Malaysian: ms_MY.UTF-8
> Indonesian: id_ID.UTF-8
> Vietnamese: vi_VN.UTF-8
Are there any pla
attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080707/8d4d280e/attachment.html>
If there's any issues with this case, please send an email before the
timeout (07/08/2008)
Thanks.
--Irene
On Wed, 2008-07-02 at 03:19 -0700, Shi-Ying Irene Huang wrote:
> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
> This information is Copyright 2008 Sun Microsystems
> 1. Introduction
What is the motivation for having SCIM as well as the already existing
IIIMF ? Is SCIM the future and IIIMF will be marked as Obsolete and
eventually removed ?
What does SCIM do that IIIMF does not (and vice versa) ?
How does a user know which system they should be using ?
--
Darren J Moffat
Alan Coopersmith writes:
> Alan Coopersmith wrote:
> > I am sponsoring this case for myself and have set the timeout to next
> > Wednesday, July 2, 2008. If anyone feels more time is needed due to
> > the upcoming US holiday, please let me know.
>
> There having been no discussion on the alias,
Darren Reed writes:
> Yes, /dev/net.
>
> The correct way to interface with /dev/net should be via libdlpi.
Agreed; not just correct but easy.
However, for some open source projects, being able to support more
than just OpenSolaris is a goal. In that case, it makes sense to use
plain old DLPIv2
I am sponsoring the following Fast Track for Bill Schoofs. The project
requests
a minor release binding. All submitted materials are in the case directory.
--
1.0 Project Information
1.1 Name of project/component
libmikmod
1.2 Author of document
Bill Schoofs
2.0 Project Summary
2.1
I am sponsoring this fast-track case for myself.
This proposal will time out 07/11/2008
All of the proposed interfaces are specified by Posix (SUSv3),
so the stability level is 'Standard' in all cases.
The proposed release binding is "minor release"
since no one wants this to be back-ported to So
Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Adding Malaysian, Indonesian, Vietnamese UTF-8 locales
1.2. Name of Document Author/Supplier:
Author: Wei Xue
20 matches
Mail list logo
