From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch
Date: Tue, 7 Dec 2004 07:06:03 +0900 [thread overview]
Message-ID: <20041206220602.GA48512@lion.gg3.net> (raw)
In-Reply-To: <20041206213702.GA18743@lion.gg3.net>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
maillog: 07/12/2004-06:37:03(+0900): Georgi Georgiev types
> maillog: 06/12/2004-10:17:55(-0800): Donnie Berkholz types
> > > 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?
>
> My point is that /usr/X11R6/lib/X11/xkb moved to /usr/lib/xkb,
> /usr/X11R6/lib/X11/modules moved to /usr/lib/modules... If xkb and
> modules had moved to /usr/lib/X11/xkb and /usr/lib/X11/modules it would
> have made more sense, but their current location is a bit confusing to
> me.
OK, in more detail:
- I now have stuff installed in
/usr/lib64/{config,etc,getconfig,modules,xkb} ... for some reasons
that I cannot pinpoint and/or articulate, these bother me.
- Without the "font-server" use flag (correct me if I'm wrong), ttmkfdir
is not installed; Do I really not need it even for a no-font-server
installation?
- No idea why, but /usr/X11R6/lib64/X11/xkb is now a symlink that points
to ../../lib/xkb, which means that it essentially points to itself
(/usr/X11R6/lib points to lib64). This could be related to the fact
that I now installed after first removing /usr/X11R6 ( "emerge -C
xorg-x11" and all packages that owned /usr/X11R6 save for baselayout
and groff, and then move /usr/X11R6 away), but the binary package I
built on a system that had xorg -r3.
I'm off to school in an hour, so I'll leave -r4 compiling on a clean (no
/usr/X11R6) system to see if at least the xkb symlink starts pointing to
a proper location.
--
\ Georgi Georgiev \ Remember, Grasshopper, falling down 1000 \
/ chutz@gg3.net / stairs begins by tripping over the first /
\ +81(90)6266-1163 \ one. -- Confusion \
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-06 22:06 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
2004-12-06 18:54 ` Hans-Werner Hilse
2004-12-06 21:37 ` Georgi Georgiev
2004-12-06 22:06 ` Georgi Georgiev [this message]
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=20041206220602.GA48512@lion.gg3.net \
--to=chutz@gg3.net \
--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