From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Ferris McCormick <fmccor@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Question about xfree86-4.3.0-r6
Date: Fri, 14 May 2004 11:21:04 -0400 [thread overview]
Message-ID: <1084548064.23934.128.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0405141330410.23632@lacewing.inforead.com>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
On Fri, 2004-05-14 at 09:49, Ferris McCormick wrote:
> I am guessing here; I don't know why it's hard masked. I suggest you look
> at the ChangeLog and address the question to spyderous.
I don't see much in the ChangeLog to give any hints. The listing in
package.mask is:
# <seemant@gentoo.org> 21 May, 2003
# Masked while it's still under development. I need revision control on
the
# thing, which is why it's in portage at all. Do NOT install this.
# 30 May, 2003 : Seems that xterm is in its own separate package as
well, so
# taking that out of -r3. Added utempter, (dep for xterm to not install
# suid)
=x11-base/xfree-4.3.0-r6
media-fonts/chkfontpath
I guess I would just like to see us using common font locations across
our 2 major X builds.
> That said:
> I think one of the reasons is the font directory change, but I am not part
> of the xfree herd, and I have no direct information.
>
> I can tell you that for sparc, it runs just like xfree-4.3.0-r5, but with
> the font move. I can also tell you that for sparc, you are better off
> bypassing 4.3.0-r6, 4.3.xx, and moving directly to xorg-x11. But I am
> not developing tools to run on both.
Actually, I am working with a tool to create working X configurations.
Currently, it works with xfree, but not xorg-x11. To get it to work
with xorg-x11 (and eventually allow us to transition that way), the
fonts need to be in the same place.
> I don't know what architectures interest you, but sparc is not likely
> to be high on your list :)
I don't know much about it, but I'll be learning much more that I
started my new position, since we have a decent amount of sparc
machines.
> (On sparc, I would say "go for it (-r6) if you need to," but I do not
> presume to suggest that is the case for anything else. I would also
> say "don't even think about 4.3.99-xxx, because it likely won't work
> the way you want, and you won't get much sympathy if you complain." But
> I am speaking for myself here.)
I don't want 4.3.99. All I want is for the fonts to be in the same
place on both X servers. ;]
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-14 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 12:31 [gentoo-dev] Question about xfree86-4.3.0-r6 Chris Gianelloni
2004-05-14 12:30 ` Ferris McCormick
2004-05-14 13:40 ` Chris Gianelloni
2004-05-14 13:49 ` Ferris McCormick
2004-05-14 15:21 ` Chris Gianelloni [this message]
2004-05-14 15:18 ` Ferris McCormick
2004-05-15 10:16 ` Donnie Berkholz
2004-05-17 11:58 ` Chris Gianelloni
[not found] ` <200405141114.01880.lv@gentoo.org>
2004-05-14 19:41 ` Chris Gianelloni
2004-05-15 9:29 ` Donnie Berkholz
2004-05-15 12:32 ` [gentoo-dev] " Javier Marcet
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=1084548064.23934.128.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=fmccor@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