[prev in list] [next in list] [prev in thread] [next in thread]
List: opensolaris-i18n-discuss
Subject: Re: [i18n-discuss] [pkg-discuss] IPS features
From: Yong Sun <Yong.Sun () Sun ! COM>
Date: 2008-08-16 1:24:46
Message-ID: 48A62C5E.1030403 () Sun ! COM
[Download RAW message or body]
Hi, Jan,
Yeah, I think it's OK to add a new attribute. :) In Synaptic (the GUI
frontend of apt-get), there is a small icon before the package name, to
indicate this package is recommended to install, e.g., ruby 1.8.6 but
not 1.9 is currently recommended as the default ruby runtime. I think
maybe we could use 'recommended=true', and this attribute could also be
used in other cases.
Regards,
Jan Trejbal 写道:
> Hello Yong,
> thank you for valuable comment. There exist also other packages which
> can be considered as un-mandatory/optional. For example non-UTF-8
> locales support (SUNWlang-XX-extra).
>
> Currently my proposal does not differ between mandatory and optional
> locale/language bits. But I think it should not be difficult to add that
> functionality. What about adding one more attribute "optional=true" to
> packages like iiimf-cle-open?
> Then, the interface can provide following functionality:
>
> zh= G11nInstall.Language("zh_CN")
> inst_filter01= zh.get_filter("mandatory_bits_only")
> inst_filter02= zh.get_filter("include_optional_bits")
>
> If you agree, I will add above described functionality to the list of
> Additional functionality of the interface.
>
>
> Regarding your second comment, the GUI tools will obtain filters or
> package names from the interface. Then, it's up to the GUI tool to call
> IPS and find out what packages/files are installed on the system and
> what is available at network repository. Using that data, installation
> status of language/locale can be displayed to user.
>
> Regards,
> Jan
>
>
> Yong Sun wrote:
>
>> Hi, Jan,
>>
>> I have a question about the mandatory and un-mandatory component for a
>> specific locale/language, e.g., we may list iiimf-cle-sunpinyin as the
>> mandatory components for Chinese language, but iiimf-cle-open is not.
>> But they maybe attached the same attributes or tags.
>>
>> And I also like to know, if the graphical user interface could give the
>> user the information if a locale/language is currently partially
>> installed, e.g., some preferred fonts is not installed from the slim
>> installer on liveCD.
>>
>> Thank you very much.
>>
>> Regards,
>>
>> Jan Trejbal 写道:
>>
>>> Hello IPS experts.
>>> I have questions about IPS, but first let me explain why I am asking
>>> those questions.
>>>
>>> I am working on proposal of a new interface which provides information
>>> about G11n (Globalization) elements, e.g. languages and locales.
>>> Including information about packaging of those elements, in order to be
>>> able to install/remove them in OpenSolaris.
>>>
>>> Consumer of the interface is for example Package manager. It will get
>>> list of available languages/locales from the interface. Later on, when
>>> user decides to install additional languages, the interface will provide
>>> IPS filter (or list of packages) which installs selected languages and
>>> locales on the system.
>>> Here is example of a filter, which installs localization for French
>>> Canadian locale (fr_CA):
>>>
>>> language=fr
>>> territory=CA
>>> encoding=UTF-8 | encoding=ISO8859-1 | encoding=ISO8859-15
>>> message=true
>>>
>>> Implementation of the interface will define/store G11n-related data at
>>> IPS as attributes and tags. The interface will be querying that data
>>> from IPS image and network repository.
>>> Here is example of data I plan to store at IPS (SUNWlang-fr package):
>>>
>>> Package attributes:
>>> set name=language value=fr
>>> set name=encoding value=UTF-8
>>> depend fmri=pkg:/SUNWlang-common type=require
>>>
>>> File tags (ULL=usr/lib/locale):
>>> PATH LANGUAGE TERRITORY ENCODING MESSAGE
>>> $ULL/fr.UTF-8/LC_MESSAGES fr UTF-8 true
>>> $ULL/fr.UTF-8/LC_MESSAGES/*.mo fr UTF-8 true
>>> $ULL/fr_FR.UTF-8/fr_FR.UTF-8.so.3 fr FR UTF-8
>>> $ULL/fr_CA.UTF-8/fr_CA.UTF-8.so.3 fr CA UTF-8
>>>
>>> See more details and examples at following documents:
>>> http://wikis.sun.com/download/attachments/45908778/design.txt
>>> http://wikis.sun.com/download/attachments/45908778/high-level.png
>>>
>>>
>>> Now my questions come. Can you please do me a favour and help me answer
>>> them?
>>>
>>> 1) Does IPS currently (or will in 2008.11) support custom tags,
>>> attributes, and filters from examples described above?
>>> Also, will interface consumers be able to use IPS filters for
>>> packages/files installation and removal?
>>>
>>> 2) Is there (Python) IPS interface, which I can call to retrieve the
>>> custom package attributes and file tags?
>>>
>>> 3) Where can I define and modify custom attributes & tags for our (G11n)
>>> packages, which were delivered to pkg.opensolaris.org and LiveCD?
>>>
>>>
>>> I also welcome any comments on design of the proposed interface. You may
>>> see a way how to make it simpler, more efficient, etc.
>>> For example, I am not sure if using Image and Repository Python objects
>>> as input, and Filter object as output of the interface is the best thing
>>> to do.
>>>
>>> Thank you,
>>> Jan
>>>
>>>
>>> _______________________________________________
>>> i18n-discuss mailing list
>>> i18n-discuss@opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/i18n-discuss
>>>
>>>
>> _______________________________________________
>> pkg-discuss mailing list
>> pkg-discuss@opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
>>
> _______________________________________________
> pkg-discuss mailing list
> pkg-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
>
_______________________________________________
i18n-discuss mailing list
i18n-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/i18n-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic