[Bug 507294] New: [RFE] Allow wildcards/regexps in yum install/upgrade/comps...

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: [RFE] Allow wildcards/regexps in yum install/upgrade/comps...

https://bugzilla.redhat.com/show_bug.cgi?id=507294

           Summary: [RFE] Allow wildcards/regexps in yum
                    install/upgrade/comps...
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: low
         Component: yum
        AssignedTo: skvidal at sethdot.org
        ReportedBy: nicolas.mailhot at laposte.net
         QAContact: extras-qa at fedoraproject.org
                CC: james.antill at redhat.com, pmatilai at redhat.com,
                    jnovy at redhat.com, tim.lauridsen at googlemail.com,
                    ffesti at redhat.com, fedora-fonts-bugs-list at redhat.com,
                    skvidal at sethdot.org
    Classification: Fedora


(this is the sister bug of ##507292 which was opened against rpm)

The problem:

Selecting a font is a multi-criterium operation. We need to match on font
family, font style, language support, unicode support, etc. At any time all of
just some of those selection criterii can be provided by the user or
applications.

To have features like font auto-installation work reliably, this matching needs
to extend to the package installation selection logic

Right now rpm is only allowing to specify atomic provides, so we can have a
font package that
Provides font(dejavusans)
and
Provides
font(:lang=el)

but there is no warranty both those provides are belonging to the same font.
There is no way to distinguish between a package that includes an actual greek
dejavusans and a package that includes a dejavusans greek-less file and another
totally different greek font

To workaround this rpm limitation we've been asking packagers to put font files
belonging to different font families in different packages. However:
1. many still don't
2. it's not technically possible for all font formats, for example the ttc font
format allows mixing of fonts with different characteristics in a single file

The ideal solution:

Ability to have Provides like:

font(comma-separated font name list|comma-separated style list|comma-separated
lang list) (rough mockup that probably needs refining)

And have package selectors like (dejavu|*|el) that work in yum

(yes a font can declare many different names, be available in many different
styles, cover many different languages)

For ttc files we'd then generate one Provides for each font included in the ttc
bundle

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.