Skip site navigation (1)Skip section navigation (2)
Date:      08 Nov 1999 01:06:04 -0800
From:      asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami)
To:        Will Andrews <andrews@TECHNOLOGIST.COM>
Cc:        ports@FreeBSD.ORG, pfgiffun@bachue.usc.unal.edu.co, "R. Imura" <imura@cs.titech.ac.jp>, se@FreeBSD.ORG
Subject:   Re: Possible change in the Qt port.
Message-ID:  <vqcaeopmjyb.fsf@silvia.hip.berkeley.edu>
In-Reply-To: Will Andrews's message of "Sun, 07 Nov 1999 04:34:13 -0500 (EST)"
References:  <XFMail.991107043413.andrews@TECHNOLOGIST.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
 * From: Will Andrews <andrews@TECHNOLOGIST.COM>

 * On 07-Nov-99 Satoshi - Ports Wraith - Asami wrote:
 * > ${PREFIX}/include/qt2/ -> ${PREFIX}/lib/qt/include/qt2/
 * 
 * Qt2 goes in its own league. You can't mix and match. (remember, Qt2 requires
 * gcc 2.95.*, whereas Qt 1.4x does not.)

Ok, but what does that have to do with moving the include files from
one segregated subdirectory to another?

 * > (the filenames are hypothetical, I don't know if qt has any
 * > executables -- just take these as examples of the idea)
 * 
 * moc is _the_ Qt binary. It's normally in ${X11BASE}/bin/.

Ok, thanks.

 * > If so, I'm against this change.  There are reasons and history behind
 * > us asking ports to conform to our hier; this runs completely counter
 * > to it.
 * 
 * hier(7) does seem to disagree with this, as neither includes nor binaries are
 * "X11 libraries".

What the jell are you talking about?  You mean this one?

> man 7 hier
 :
              X11R6/    X11R6 distribution executables, libraries, etc (op-
                        tional).
 :

 * I think the BIGGEST problem with Qt / KDE is the way KDE has its stuff
 * installed into ${LOCALBASE} instead of ${X11BASE}, like Qt does. Many ports
 * depend on both Qt and KDE libraries/includes, making it extremely difficult for
 * a port to know where to install things.

Hmm.

 * I propose that KDE be moved to ${X11BASE}, all of it. Why it was put into
 * ${LOCALBASE} in the first place is beyond me.

KDE is a pretty X-centric package, I personally have no problem with
moving them to ${X11BASE}.

I believe the reason why it was put into ${LOCALBASE} was because the
default Makefiles that come with KDE want to install into
${LOCALBASE}/kde which Stefan (KDE maintainer) changed to
${LOCALBASE}.  Is that the only reason why it's in ${LOCALBASE} and
not ${X11BASE}, Stefan?

-PW


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcaeopmjyb.fsf>