* From: "R. Imura" [EMAIL PROTECTED]
* kdm determines X path as 'test -f $PATH/bin/X', so touching X is enough.
*^^^ $PATH/X
Well, I don't want to add a dysfunctional file in the tarball (what if
some port does a "test -x X"?) so I just added X
* It's because, there are no /usr/X11R6/bin/X in Asami-san's chroot
* environment, I bet.
Hmm. So kdm looks at the X symlink to decide whether to build with X
support or not?
I can add that to my X package, but what exactly do I need? Just the
symlink (to nowhere), or do I need it
kdm determines X path as 'test -f $PATH/bin/X', so touching X is enough.
^^^ $PATH/X
-- R. Imura
// my private mail address has changed.
// [EMAIL PROTECTED] [EMAIL PROTECTED] /(-.-)y-~~
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
* From: "R. Imura" [EMAIL PROTECTED]
* It's because, there are no /usr/X11R6/bin/X in Asami-san's chroot
* environment, I bet.
Hmm. So kdm looks at the X symlink to decide whether to build with X
support or not?
I can add that to my X package, but what exactly do I need? Just the
symlink
For a long time I have noticed that when I build kdm from the kdebase
port, it works.
But if I used packages off either the CDs or ftp sites, it doesn't work.
Specifically if I
do a 'strings' on the binary and grep for /, some of the paths I see
have XBINDIR
rather than explicit references to
