From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: font.eclass add Xorg FontPath elements for non-standard paths
Date: Fri, 5 Jul 2013 13:41:23 +0800 [thread overview]
Message-ID: <CAB9SyzQRyba8ZuDnsKc8MFcMqc=i0qT2UYQxw4sVWU1wZQgd6A@mail.gmail.com> (raw)
In-Reply-To: <20130704163628.2967e756@caribou.gateway.2wire.net>
On 5 July 2013 06:36, Ryan Hill <dirtyepic@gentoo.org> wrote:
>
> What you want is the font path element catalog and /etc/X11/fontpath.d (bug
> #185264) which I abandoned when I realized that no one actually uses fontpath
> anymore, that it caused the startup time to drastically increase with the
> number of installed fonts, and that adding your own fontpath entries is both
> trivial and documented everywhere.
>
We should probably add this to our documentation, and link to that
from a post-install message (using readme.gentoo.eclass).
--
Cheers,
Ben | yngwin
Gentoo developer
next prev parent reply other threads:[~2013-07-05 5:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 23:07 [gentoo-dev] font.eclass add Xorg FontPath elements for non-standard paths Michael Weber
2013-07-04 6:24 ` About teams having inactive people (Was:Re: [gentoo-dev] font.eclass add Xorg FontPath elements for non-standard paths) Pacho Ramos
2013-07-04 9:26 ` Markos Chandras
2013-07-04 10:09 ` [gentoo-dev] font.eclass add Xorg FontPath elements for non-standard paths Michael Weber
2013-07-04 12:10 ` Gilles Dartiguelongue
2013-07-04 12:24 ` Michael Weber
2013-07-04 14:33 ` Michael Weber
2013-07-04 14:45 ` Fabian Groffen
2013-07-04 14:48 ` Michael Weber
2013-07-04 19:42 ` Michał Górny
2013-07-04 22:36 ` [gentoo-dev] " Ryan Hill
2013-07-05 5:41 ` Ben de Groot [this message]
2013-07-05 6:37 ` [gentoo-dev] " James Cloos
2013-07-05 7:18 ` Michael Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB9SyzQRyba8ZuDnsKc8MFcMqc=i0qT2UYQxw4sVWU1wZQgd6A@mail.gmail.com' \
--to=yngwin@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox