Idea: "{Gnome,KDE,Xfce,...} Minimal Desktop" groups

[Sandro Mani]

On 03.05.2013 14:20, Nicolas Mailhot wrote:
> Le Mer 1 mai 2013 02:17, Sandro Mani a écrit :
>> On 01.05.2013 02:08, Felix Miata wrote:
>>> On 2013-05-01 01:37 (GMT+0200) Sandro Mani composed:
>>>
>>>>> # yum install @critical-path-gnome
>>>> The gnome one is close, the kde one not: critpath contains kdelibs and
>>>> kdm, but a minimal set would rather look like
>>>> base + xorg + mesa + kdm kde-workspace dejavu-sans-fonts
>>>> dejavu-sans-mono-fonts
>>>> (here it might be a good idea to have the dejavu-sans-fonts as
>>>> dependencies of kdm / kde-workspace?)
>>> Why only DejaVu (which along with Verdana and Vera have the
>>> significantly largest average x-height and width of common western web
>>> fonts)?
>>>
>> Aren't the dejavu fonts those which are mapped to the standard sans,
>> serif and monospace fonts? (could very well be wrong here).
>>> What good are TTF/OTF fonts without Xorg?
> Most our fonts are mapped to the relevant generic aliases, mapping them is
> part of our standard font packaging process. Dejavu tend to be preferred
> over other fonts when installed because it has decent glyphs for a lot of
> scripts, but nothing prevents you from running a Fedora system with other
> fonts now (or even specifying different priorities in /etc). A lot of
> other fonts have 'nicer' glyphs for specific scripts. What they usually
> lack is consistent quality over large coverage, it's easy to draw a few
> hundred glyphs, i18n requires a lot more.
>
> Hardcoding specific fonts in package deps only leads to sterile debates
> about the best font to hardcode, and always angers part of the users,
> since none of the existing fonts has wide and good enough coverage to
> satisfy all user groups (that's why @fonts is a group with *lots* of
> default entries).
>

Thanks for the explanation!