Danek Duvall wrote:
> On Wed, Jul 23, 2008 at 03:05:48PM +0900, Takeshi Asano wrote:
>
>
>>> Yong Sun wrote:
>>>
>>>> I once posted a query to pkg alias and CC'd to you, if we could specify
>>>> a filter as following,
>>>>
>>>> |(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,...) |
>>>>
>
> What are you trying to express here?
>
Sorry, there is a format issue, the filter should be
(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,...)
The meaning I wan to express is to install the docs and messages for
openoffice as well as all installed packages (may already include oo),
and the specified packages 'lang-french-support' and 'ttf-french-fonts'.
It's a combined filter, so that I could use such a filter to install all
necessary contents in one-step. This filter could be extracted to a
conjunctive normal form or disjunctive normal form.
Regards,
> You can have image-level filters, which apply to all packages, and you can
> have package-level filters that apply to individual packages.
>
> So you could have an image-level filter which says
>
> arch=i386
> locale=fr
> doc=true
>
> which would give you all files which were tagged as being x86 binaries (as
> well as those which weren't tagged with an architecture at all), all files
> tagged with the french locale (or none at all), and all files tagged as
> being documentation (or not tagged as docs at all).
>
> You could have a separate filter for openoffice:
>
> arch=i386
> locale=fr | locale=de
> doc=true
>
> which would add german localizations to the openoffice installation.
>
> There are a number of enhancements that we'll likely need to make to
> filters as we begin to use them more. For instance, it would be nice to
> be able to express fallback options, such as preferring fr_CA.UTF-8, but if
> something is only tagged as fr_CA, or even just fr, that would be fine.
>
> We may also need for package-level filters to pass on to dependencies.
>
>
>>>> 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).
>>>
>
> Yup, that's certainly a possibility, though I could see a single font
> family being delivered by a single package, and having individual font
> files being tagged with what locales they're useful in.
>
> Danek
>
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss