public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch
Date: Mon, 06 Dec 2004 10:17:55 -0800	[thread overview]
Message-ID: <1102357075.14214.4.camel@localhost> (raw)
In-Reply-To: <20041206154223.GA19994@lion.gg3.net>

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

On Tue, 2004-12-07 at 00:42 +0900, Georgi Georgiev wrote:
> maillog: 06/12/2004-02:48:55(-0800): Donnie Berkholz types
> > Hey everyone,
> > 
> > If anybody has good reasons why -r4 shouldn't be unleashed upon the
> > unsuspecting ~arch users, respond to this (on-list please) before 0000
> > UTC Wednesday. Why then? Well, my finals will be over, so I'll have time
> > to deal with the expected deluge of reports.
> 
> I gave -r4 a shot yesterday on my amd64. A few problem I encountered:
> 
> - xterm could not compile properly and was giving me the "locale not
>   supported; could not open input method" errors. I haven't looked into
>   the problem in detail

No idea -- I just compiled xterm-196-r1 yesterday with it.

> - the default xorg.conf that came with it had
>   `FontPath "/usr/lib64/fonts/..."' which I belive has something to do
>   with the default "/usr/X11R6/lib/X11/fonts/..." in -r3, which has to
>   be "/usr/share/fonts" anyway.

Any idea why this wouldn't catch it?

    # Fix default config files after installing fonts
to /usr/share/fonts
    sed -i -e "s:/usr/X11R6/$(get_libdir)/X11/fonts:/usr/share/fonts:g"
\
        -e "s:/usr/$(get_libdir)/X11/fonts:/usr/share/fonts:g" \
        ${D}/etc/X11/xorg.conf.example

> 
> Other than that it worked straight out of the box. Not sure why the xkb
> directory was also moved to /usr/lib64/xkb though.

Everything in /usr/X11R6/lib moved. /usr/X11R6/lib is now a symlink.
Therefore, xkb moved along with it. Am I misunderstanding something?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-12-06 18:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 10:48 [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch Donnie Berkholz
2004-12-06 15:42 ` Georgi Georgiev
2004-12-06 18:17   ` Donnie Berkholz [this message]
2004-12-06 18:54     ` Hans-Werner Hilse
2004-12-06 21:37     ` Georgi Georgiev
2004-12-06 22:06       ` Georgi Georgiev
2004-12-06 22:17         ` Georgi Georgiev
2004-12-06 23:10           ` Donnie Berkholz
2004-12-07  0:38         ` Donnie Berkholz
2004-12-07  1:01           ` Georgi Georgiev
2004-12-07  3:01             ` Donnie Berkholz
2004-12-07  2:17           ` Donnie Berkholz
2004-12-07  1:27 ` Georgi Georgiev
2004-12-07  1:37 ` [gentoo-dev] HOSTCONF in global scope Georgi Georgiev
2004-12-07  1:52 ` [gentoo-dev] Double stripping in strip_execs() Georgi Georgiev
2004-12-07 12:34 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch -- ~sparc OK Ferris McCormick
2004-12-07 19:59 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch --- ~sparc tests good Ferris McCormick
2004-12-07 22:52   ` Georgi Georgiev
2004-12-07 23:02     ` Georgi Georgiev
2004-12-07 23:36       ` Ferris McCormick
2004-12-08  0:16         ` Georgi Georgiev
2004-12-08  0:38           ` Donnie Berkholz
2004-12-08  2:19             ` Georgi Georgiev

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=1102357075.14214.4.camel@localhost \
    --to=spyderous@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