Yo,
--- Christopher Molnar <[EMAIL PROTECTED]>
wrote:
> I think this being "screwed up" is open for debate.
> Please let me know
> what isn't working for you?
>
path convention :), actually a bit more serious than
that. include files should go in /usr/include
/usr/local/include, it's always been teh convention, i
don't think it would be very nice if we break it.
besides, it's not just about cooker, others may be
compiling their own apps and specifying the include in
/usr/include
> Placing the files in /usr/include/qt2 makes it
> impossible to user the
> QTDIR variable when compiling aps that require it.
> licq has also been
> recompiled and fixed.
>
i see. but licq is in the distro, how about other qt2
apps that some users may be using that are _OUT_ of
the distro? you'll be breaking those. and users won't
like that.
> As it is QTDIR=/usr/lib/qt2 works well. Nothing
> seems to be broke. Final
> test: KDE2 compiles very well.
>
> I also have uploaded a fix last night as I forgot a
> linked file.
>
let's say we go for a compromise? let's put the files
in /usr/include/qt2, and we do a symlink in /usr/lib ?
i'm saying that the files should go in
/usr/include/qt2 (and i think it's important that they
go there), because that's where they belong. i
particularly don't like the idea of finding header
files in /usr/lib ...urgh. but having a symlink in
/usr/lib/qt2 --> /usr/include/qt2 will, as you say,
simpify compilation of applications since you can use
the env variable now.
Snail.
__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com
