public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@gentoo.org>
To: Chris Gianelloni <wolf31o2@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Question about xfree86-4.3.0-r6
Date: Fri, 14 May 2004 13:49:36 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405141330410.23632@lacewing.inforead.com> (raw)
In-Reply-To: <1084542037.23934.54.camel@localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 14 May 2004, Chris Gianelloni wrote:

> On Fri, 2004-05-14 at 08:30, Ferris McCormick wrote:
> > > Does the xfree86-4.3.0-r6 ebuild also have the fonts moved to
> > > /usr/share/fonts like the xorg-x11-6.7.0 does?
> > >
> > 
> > Yes.
> 
> Excellent, so why is it still hard masked exactly?  I haven't been
> following the problems with it, so consider me completely uninformed on
> the situation.
>
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.

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.

I don't know what architectures interest you, but sparc is not likely
to be high on your list :) 

(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.)
 
> All I am trying to do is work on a tool or two that I would like to be
> usable for both xfree and xorg-x11, but currently, the font path
> difference is a major bug/annoyance.
> 

That I believe.

> -- 
> Chris Gianelloni
> Developer, Gentoo Linux
> Games Team
> 
> Is your power animal a penguin?
> 

- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFApM5zQa6M3+I///cRAvi+AKCFuKo5Lld2uNsdzC2Opl1af6UyUgCcCSxT
RxaKhMXhWqZZgtA8DjRS/a4=
=0eWN
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-14 14: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 [this message]
2004-05-14 15:21       ` Chris Gianelloni
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=Pine.LNX.4.58.0405141330410.23632@lacewing.inforead.com \
    --to=fmccor@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wolf31o2@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