I know there have been problems, but are we any nearer getting the backend stuff yet?
Anne
Hello Anne,
On Saturday 10 October 2009, 05:38, Anne Wilson wrote:
I know there have been problems, but are we any nearer getting the backend stuff yet?
don't know about Fedora-KDE, but upstream is working on Virtuoso backend for 4.4 http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/
Regards
2009/10/10 Ariel Constenla-Haile ariel.constenla.haile@googlemail.com:
Hello Anne,
On Saturday 10 October 2009, 05:38, Anne Wilson wrote:
I know there have been problems, but are we any nearer getting the backend stuff yet?
don't know about Fedora-KDE, but upstream is working on Virtuoso backend for 4.4 http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/
rdieter had a try out on it. It was "working" so far and will hit kde-unstable from what he wrote in IRC. So we can play with it ;)
Thomas Janssen wrote:
rdieter had a try out on it. It was "working" so far
and will hit
kde-unstable from what he wrote in IRC. So we can
play with it ;)
FYI:
virtuoso-opensource virtuoso-opensource-apps virtuoso-opensource-conductor virtuoso-opensource-utils
are already in the repo, assuming you are using f11.92 (rawhide), as I am.
I installed the first: it gives me ratings, comments and tags in the dolphin information panel.
I guess I should see about installing some of the other virtuosi to see if there is something more useful possible.
2009/10/10 Petrus de Calguarium kwhiskerz@gmail.com:
Thomas Janssen wrote:
rdieter had a try out on it. It was "working" so far
and will hit
kde-unstable from what he wrote in IRC. So we can
play with it ;)
FYI:
virtuoso-opensource virtuoso-opensource-apps virtuoso-opensource-conductor virtuoso-opensource-utils
We're speaking of the Soprano Backend.
Thomas Janssen wrote:
We're speaking of the Soprano Backend.
Just following the discussion. The trueg.wordpress.com link provided earlier in this thread refers to virtuoso and virtuosobackend (not that I have a clue what the difference is between all of this stuff -- just trying to learn how to get it working and whether it actually does anything useful, which, as yet, remains to be seen, given the lack of evidence so far).
For reference:
Ariel Constenla-Haile wrote:
don't know about Fedora-KDE, but upstream is working on Virtuoso backend for 4.4 http://trueg.wordpress.com/2009/10/09/virtuoso-for-
real/
Hello Petrus,
On Saturday 10 October 2009, 15:54, Petrus de Calguarium wrote:
Thomas Janssen wrote:
We're speaking of the Soprano Backend.
Just following the discussion. The trueg.wordpress.com link provided earlier in this thread refers to virtuoso and virtuosobackend (not that I have a clue what the difference is between all of this stuff --
this week there have been some blogs about Nepomuk at al.
http://thomasmcguire.wordpress.com/2009/10/03/akonadi-nepomuk-and-strigi-exp... http://tokoe-kde.blogspot.com/2009/09/pimp-my-nepomuk.html http://mat69.wordpress.com/2009/10/03/nepomuk-is-useful-but-is-it-useable
just trying to learn how to get it working
you won't make the Virtuoso backend work, it depends on KDE trunk (= you have to download the source from SVN and build it yourself).
You can test which backend Nepomuk is using by perfoming on a terminal (with Nepomuk running, of course )
qdbus org.kde.NepomukStorage /nepomukstorage usedSopranoBackend
in Fedora this will output redland
Regards
Ariel Constenla-Haile wrote:
this week there have been some blogs about Nepomuk at al.
I will have a gander. As always (after all, I always use fedora-testing, kde-unstable or rawhide), I am curious about the marvels that await :-)
I am not up to building packages from source from SVN and the like. I will wait until the packages provided by this distro reach that level of maturity.
Yes, the command did output 'redland'.
Thanks kindly.
Ariel Constenla-Haile wrote:
you won't make the Virtuoso backend work, it depends on KDE trunk (= you have to download the source from SVN and build it yourself).
Which is a painful arduous task even with the kdesvn-build scripts, if you don't know what you're doign... aka, i've been trying to make this happen for a week ^_^
Ariel Constenla-Haile wrote:
you won't make the Virtuoso backend work, it depends on KDE trunk (= you have to download the source from SVN and build it yourself).
No, it doesn't need KDE trunk, only Soprano trunk. rdieter is going to put that into kde-redhat unstable too.
Kevin Kofler
Hello Kevin,
On Sunday 11 October 2009, 14:22, Kevin Kofler wrote:
Ariel Constenla-Haile wrote:
you won't make the Virtuoso backend work, it depends on KDE trunk (= you have to download the source from SVN and build it yourself).
No, it doesn't need KDE trunk, only Soprano trunk.
yes, it does: "...And then once you have updated your *kdebase* copy to the latest *trunk* ... " http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/
in the last week there have been several changes in kdebase/runtime/nepomuk ... and kdebase from trunk depends on kdelibs from trunk, so you need kde trunk. Resume: you need at least kdelibs, kdepimlibs and kdebase from KDE trunk, and a recent snapshot of Virtuoso.
Regards
Ariel Constenla-Haile wrote:
"...And then once you have updated your *kdebase* copy to the latest *trunk* ... " http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/
Yet... http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/#comment-623
| Alejandro Nova | The question that everyone is asking now: | May we use Soprano 2.3.63 with KDE 4.3? This is the solution for all | NEPOMUK headaches with Fedora. | | Sebastian Trüg | Soprano 2.4 is fully backwards compatible, so yes.
in the last week there have been several changes in kdebase/runtime/nepomuk ... and kdebase from trunk depends on kdelibs from trunk, so you need kde trunk
If any of the bugfixes from: http://websvn.kde.org/trunk/KDE/kdebase/runtime/nepomuk/?view=log are actually needed, we can just backport them. In fact I think building just kdebase/runtime/nepomuk from trunk should just work (but building parts of kdebase-runtime is of course a bit more work than cmake; make; make install; the simplest way is for us to simply patch our kdebase-runtime package).
Kevin Kofler
Hello Kevin,
On Sunday 11 October 2009, 18:57, Kevin Kofler wrote:
in the last week there have been several changes in kdebase/runtime/nepomuk ... and kdebase from trunk depends on kdelibs from trunk, so you need kde trunk
If any of the bugfixes from: http://websvn.kde.org/trunk/KDE/kdebase/runtime/nepomuk/?view=log are actually needed, we can just backport them. In fact I think building just kdebase/runtime/nepomuk from trunk should just work (but building parts of kdebase-runtime is of course a bit more work than cmake; make; make install;
/me dummy cmake && make && make install Last time I mixed libraries from trunk and a branch I ended up with kdevelop and dolphin crashing every time; so I do a clean build (not every week, I'm not that freak - I'm still running a KDE/4.3.69 svn-1027783; 2009-09-23).
Regards
Ariel Constenla-Haile wrote:
/me dummy cmake && make && make install
Isn't it bad form to build as root? :-)
Ariel Constenla-Haile wrote:
/me no root: install & run from /home/ariel/kdetrunk
Aha, I should've known that... :-) Bedtime I suppose