Sorry corrected typo in CC'ed pkg-discuss address. Takeshi Asano wrote: > Hi Yong, > > Yong Sun wrote: >> Hi, Takeshi, >> >> I once posted a query to pkg alias and CC'd to you, if we could specify >> a filter as following, > > Sorry I couldn't catch and respond it at that time. > >> |(arch=i386 | arch=generic) & | >> | (packages=openoffice & locale=fr & (doc=true | message=true) || >> | packages=all-installed & locale=fr & (doc=true | message=true) || >> | packages=lang-french-support,ttf-french-fonts,...) | >> >> I think we may not be able to combine all l10n packages with base >> packages, like the locale enabling, and fonts. > > Right, some l10n components might not have clear corresponding > base package and keeping l10n package(s) could be option for them. > > Fonts or input methods are candidates of those stay in separate > l10n package(s). > > Some locale enabler (like libc locale shared objects) theoretically > can have corresponding base package, but it may not be practical > to merge them into the base package. > > Thanks, > Takeshi > >> Regards, >> >> Takeshi Asano wrote: >>> Hi i18n folks, >>> >>> I'd like to hear how you think about a possible l10n >>> packaging style change. >>> >>> Currently, in many cases localization (l10n) contents are >>> packaged separately from components the l10n are for. >>> >>> e.g. >>> component AAA in package aaa >>> l10n for the component (in German) in package aaa-l10n-de >>> l10n for the component (in Thai) in package aaa-l10n-th >>> : >>> If user wants to have German localization for the component, >>> he/she installs aaa and aaa-l10n-de. >>> >>> This "separate l10n packaging" is same as traditional style >>> in Nevada (or Solaris releases). >>> >>> However, IPS'es "filter" mechanism allows to install some >>> (not all) contents in a package, by specifying criteria >>> (e.g. architecture, debug-enabled, ...) >>> http://opensolaris.org/sc/src/pkg/gate/doc/filter.txt >>> >>> Utilizing this mechanism for selecting l10n files >>> enables to put l10n together with the component and user >>> can install any (one or more) l10n for the component as well, >>> especially for l10n files which have clear corresponding component. >>> >>> e.g. >>> component AAA in package aaa >>> l10n for the component (in German) in package aaa >>> l10n for the component (in Thai) in package aaa >>> : >>> But an user choose to install the package with only German >>> localization. >>> >>> Will clarify details, implemtation issues, etc. but >>> I'd like to hear if this idea basically sounds good >>> or reasonable to you or you see problem. >>> >>> Thanks, >>> Takeshi >>> _______________________________________________ >>> i18n-discuss mailing list >>> [EMAIL PROTECTED] >>> http://mail.opensolaris.org/mailman/listinfo/i18n-discuss >>> >> _______________________________________________ >> i18n-discuss mailing list >> [EMAIL PROTECTED] >> http://mail.opensolaris.org/mailman/listinfo/i18n-discuss > > _______________________________________________ > i18n-discuss mailing list > [EMAIL PROTECTED] > http://mail.opensolaris.org/mailman/listinfo/i18n-discuss
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
