Message: previous - next
Month: February 2012

Re: [trinity-users] kaffeine-3.5.13 compilation error

From: "roman" <lists@...>
Date: Wed, 1 Feb 2012 16:16:14 +0100

On Wed, February 1, 2012 14:14, E. Liddell wrote:
> My understanding is that it would go under /usr . . . somewhere.
> (ref: )
> /usr/kde/3.5 is definitely not right, though--we probably want
> /usr/tde/[version]
> or /usr/trinity/[version], for consistency.
Mhh i already gave a lecture on linux filesystem-layouts but i have no
idea what would be the better solution fsfe-wise. Personally i tend to

> QT4 actually spatters files all over the place, including locations like
> /usr/bin
> (I ran equery files qt-core while I was trying to find out where the moc
> was . . .)
Mhh my guess is we need to put qt3 in a seperate directory (or should be
keep it in /usr/qt/3 ?) otherwise there will be tons of complications.

> I'll have a look--I do have cmake ebuilds for kdeartwork and most of
> kdegraphics, although they need a bit of cleanup for mirror stuff.
Not much in there yet, just the thirdpartymirrors and an empty
documentation folder.

> Another thing that needs to be looked at is package taxonomy--we
> should consider replacing the kde-base and kde-misc categories with
> trinity-base and trinity-misc or the like, although I'm not sure exactly
> how adding whole categories works.  I'm also looking at changing the
> names of the eclasses (kde-functions -> tde-functions or
> trinity-functions,
> etc.)
Definitly! I would go with tde-* it's less typing.;) But i wouldn't want
to change stuff like "konqueror" to "tonqueror" *g.

I hope i can start going over the whole thing this evening or on

> Yes, there were a few posts a while back that indicated a couple of people
> were interested (kaffeine was mentioned in particular).  I didn't get the
> impression that they were devs, but they might at least be willing to help
> test.
It's on my TODO for the weekend.

>> >> > Say, which arch are you on?
>> >> I'm on amdfam10.
>> >
>> > *Ah.*  While my actual machine is also amdfam10, the virtual machine
>> > I've been using to test Trinity is set up as x86, not x86_64.  So we
>> may
>> > be seeing a pointer cast that works under 32bit but breaks with 64bit.
>> > (And if I were just a bit better with this, that might be enough to
>> tell
>> > me
>> > how to fix it . . .  Grrr.)
>> Probably an arch-dependant error.. i can test this again on x86 this
>> week
>> and then report upstream/open a bug-report.
> Sounds like a plan.
I always keep a stage4 somewhere;)

> I found the problem, actually:  QT4 installs its moc (and some other
> stuff,
> but I think it's the moc that's causing the breakage) to /usr/bin, which
> is
> normally going to come very early in the path.  Having each ebuild
> temporarily
> rearrange the path so that the QT3 dirs come before /usr/bin, and
> therefore
> the QT3 moc is used, might fix things.  The alternative would be patching
> the make/cmake files to specify the moc by full path, but that's a lot
> more
> complicated (and might break under some circumstances).  I wish I knew
> how kde-sunset deals with this . . .  I guess that's another thing to ask
> on
> gentoo-desktop.
Yes, i think there is at least a cmake-option or variable in the eclass
that specifies the moc-location or the kde-prefix to use.
But currently i seem to be having another little problem with the tdesktop
not wanting to run commands via ALT+F2. Will have to revisit this later
when the groundworks are there.