From: Ryan Shaw <ryan.shaw@stanfordalumni.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] ebuilds which install fonts
Date: Mon, 20 May 2002 16:40:54 +0900 [thread overview]
Message-ID: <20020520164054.46556c69.ryan.shaw@stanfordalumni.org> (raw)
i would like to create some ebuilds for some
free font collections, but i am not sure what
the standard is for ebuilds which install
fonts. the ebuilds i have seen thus far
which install fonts (freefonts and x11fonts-jmk)
create new subdirectories of of /usr/lib/X11/fonts.
this seems bad though, since it means that
a new FontPath needs to be added to XF86Config
every time new fonts are installed. why not
just stick to the standard approach of adding
fonts to the subdir of /usr/lib/X11/fonts which
matches their type (Type1, truetype, etc.) and
rebuilding the proper index files for fonts of
that type?
ryan
next reply other threads:[~2002-05-20 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 7:40 Ryan Shaw [this message]
2002-05-20 7:57 ` [gentoo-dev] ebuilds which install fonts Bjarke Sørensen
2002-05-20 8:15 ` Ryan Shaw
2002-05-20 8:33 ` Bjarke Sørensen
2002-05-20 9:16 ` Ryan Shaw
2002-05-20 12:01 ` maarten
-- strict thread matches above, loose matches on Subject: below --
2002-05-20 15:15 nate
2002-05-20 16:59 Nathaniel Grady
2002-05-21 0:27 ` Ryan Shaw
2002-05-21 6:21 ` Bjarke Sørensen
2002-05-21 6:48 ` Ryan Shaw
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=20020520164054.46556c69.ryan.shaw@stanfordalumni.org \
--to=ryan.shaw@stanfordalumni.org \
--cc=gentoo-dev@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