I built and installed sip 4.12.1 and pyqt3 x11_gpl_3.18.1.
Building pykde3 3.16.7 fails.
I built these packages last autumn with no issues. I'm using upstream sources, same as last year.
Here is a link to the build log:
http://humanreadable.nfshost.com/files/pykde3-3.16.7-i486-1-build.log.gz
I realize kdebindings is not essential to running Trinity. :)
Darrell
Guys,
The following applications need to find homes in the menu. I have give
proposed "move to" locations below. This shouldn't be confused with Kate's
effort to revise the default entries. This is just to put the existing apps with
no default kmenu location -- somewhere:
Graphics
\
More Applications
\
kruler (move to Graphics)
System
\
More Applications
\
File Manager - Super User Mode (move to System or System/Super-User)
Terminal Program - Super User Mode (move to the same place)
Utilities
\
More Applications
\
KFontView - Font Viewer (move to Graphics)
Just fixing these 4 default entries will get rid of the 'More Applications'
menu entries for these apps and give them a proper home in the menu.
If somebody will point me to the right file where this takes place, I'll work
on a patch. I suspect that the entry is specified somewhere in the individual
app build directory. I'll look at kruler and see if I can find it. If you
already know where the menu entries are set by default, please let me know. Thanks.
--
David C. Rankin, J.D.,P.E.
Tim, Robert, Serghei, Ilya, all:
Here are patches for kdelibs, kdebase, kdegraphics and kdepim that fix the
kmenu applications entries that were ending up under "More Programs" submenus
because they didn't have a home. The files affected are:
kdelibs:
kdelibs/kded/applications.menu
kdebase:
kdebase/konsole/konsolesu.desktop
kdebase/konqueror/konquerorsu.desktop
kdebase/kcontrol/kfontinst/viewpart/kfontview.desktop
kdepim
/home/david/tblds/trinity-kdepim/korn/KOrn.desktop
kdegraphics
/home/david/tblds/trinity-kdegraphics/src/kdegraphics/kruler
Screenshots of the System and Internet kmenu entries are here:
http://www.3111skyline.com/dl/dt/trinity/ss/trinity-kmenu-SystemSU.jpghttp://www.3111skyline.com/dl/dt/trinity/ss/trinity-kmenu-InternetEmail.jpg
A new custom 'Category' of 'X-KDE-System-su' was created in applications.menu
to accommodate the SuperUser submenu.
Go ahead an apply the patches to a work copy and see what you think. It all
works as it is supposed to. The xfw, xfi, etc.. apps still need to be moved out
of 'Utilities' to a submenu. I'm thinking Utilities/X-Utilities unless somebody
has a better idea.
Getting rid of the "More Applications" submenus really makes Trinity start to
look like a (getting)-finished product.
Ilya, look over what I did and make sure it is all OK. I did it using
http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html as a reference, so
it should be close. The only thing there wasn't a clear reference for was adding
the:
<Directory>kde-system-su.directory</Directory>
entries in applications.menu. Looking at all the other entries, that looks like
what was needed. Let me know. Thanks.
Enjoy :)
--
David C. Rankin, J.D.,P.E.
Trying to build arts with cmake. I received the following message:
"ALSA support are requested, but not found on your system"
Looking at the CMakeLists.txt file, I see the script is checking for "alsa/asoundlib.h."
ALSA is indeed installed and working well here. On Slackware 12.2 that file exists at:
/usr/include/alsa/asoundlib.h
/usr/include/sys/asoundlib.h
How do I fix?
BTW, you might want to change the error message from:
ALSA support are requested, but not found on your system
To:
ALSA support requested, but not found on your system
The latter is more grammatically correct in English. :)
Darrell
Guys,
After researching the freedesktop Menu Specification and Desktop Entry
Specification, I though it would be nice to have a page to make these links
available for others to use rather than just putting them in my bookmarks. That
way somebody else doesn't have to spend the 10-20 minutes searching the next
time a menu or desktop entry questions comes up.
If you are doing research for a particular issue and come up with a link that
provides a proper specification or howto that can help other Trinity devs out,
please drop the link on the page. If you can help save somebody else 30 minutes
of searching or googling to come up with an answer -- that's 30 minutes more
that they can put to fixing bugs or cmake files.
Think of this page as a "Bookmarks for Trinity Developers" page:
http://trinity.pearsoncomputing.net/wiki/bin/view/Specifications/Developmen…
To drop a new link, just 'edit' the page, 'copy/paste' an existing heading to
create a new one (change the names) and add your link. That simple. External
link format in foswiki is just:
[[http://path/to/whatever.html Then The Title You Want Displayed]]
Takes ~ 20 secs to edit,add an entry, and save :)
--
David C. Rankin, J.D.,P.E.
Hi all,
Because the trinity-devel list is flooded so much with cmake problems
and such, we're showing the lack of coordination within the project.
Therefore, I am proposing a weekly meeting:
* Takes place on irc.freenode.net, although I do not have a meetbot to
wire up, so this may be a bad idea (i do not think tbottu can do
meetbot)
* Takes place on something like iEtherpad, where we can chat and
create a checklist for the week. (trinity.ietherpad.com is taken, but
we can come up with something)
This way, the coordination is here, and there are weekly tasks.
Most importantly, we'll be able to see who is working on what and
such. (hehe! remember due dates? >:P)
I would really like your suggestions.
(if you are wondering about iEtherpad, go check it out!)
--
later, Robert Xu
Checked out revision 1224111.
==> SVN checkout of revision 1224111 -- Complete.
Scanning dependencies of target utility-static
[ 10%] Building CXX object
quanta/utility/CMakeFiles/utility-static.dir/quantacommon.cpp.o
[ 10%] Building CXX object
quanta/utility/CMakeFiles/utility-static.dir/tagaction.cpp.o
/build/src/kdewebdev/quanta/utility/tagaction.cpp:1285:25: fatal error:
myprocess.moc: No such file or directory
compilation terminated.
make[2]: ***
[quanta/utility/CMakeFiles/utility-static.dir/tagaction.cpp.o] Error 1
make[1]: *** [quanta/utility/CMakeFiles/utility-static.dir/all] Error 2
make: *** [all] Error 2
Aborting...
Build is out of source in a separate build directory
Any idea?
Thanks
I realize everybody involved here is busy in one way or another. I appreciate all efforts.
Despite my recent impatience, Trinity is my hope for a usable desktop environment in free/libre software.
For the past several days I have been exploring Xfce and KDE4 as desktop alternatives. (I never have been a Gnome person.) Just exploring the option because I never used either in any meaningful fashion.
I find myself repeatedly agitated and frustrated by both desktops. A desktop should never get in the user's way. Ever.
Xfce is impotent. Simple configuration options such as setting the menu to include descriptions or disabling tool tip popups are either impossible or must be performed with a text editor.
KDE4 is a nightmare of complexity that a significant number of everyday users never will need or even fathom.
Trinity has an opportunity to be a splendid desktop for the masses.
I realize much work remains to port the Trinity build process to cmake. There also is a large list of bugs that need quashing.
I will do what I can to build and test packages.
I will continue waddling along the next few months until the cmake transition is complete and a major bug quashing effort occurs. Yet I hope in a few month's time I find myself tickled pink from using Trinity 3.5.13. With the major effort in cmake, Trinity should remain usable and buildable for a long time.
I hope Trinity becomes successful.
To those of you involved in this process, please keep up the good work! :)
And thank you!
Darrell
Can newer releases of a distro be run in a chroot from within an older release? What problems will occur?
I'm running Slackware 12.2, mostly because that was the last release supporting KDE 3.5.10. I run my Trinity builds in a chroot.
I would like to start Trinity build testing for the most recent Slackware release.
I can run newer releases in a virtual machine, but I find virtual machines much slower than the chroot.
Thanks.
Darrell