| Line 12: | Line 12: | ||
[[MaryEllenFoster]] has been working on packaging the Java based Sesame2 backend for Nepomuk to replace the Redland backend. Unfortunately, Sesame2 is dependent on many other Java packages which must first be packaged for inclusion in Fedora. There are many packages that still need to be packaged for this backend to make it into Fedora<ref>https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame</ref>. Mary Ellen has been working hard to package many of these dependencies, but this has recently fallen in priorities to personal business. Now that she has more time to put into this packaging,<ref>http://mairi-ruadh.livejournal.com/62989.html</ref> she has realized that many of the packages on her wiki page were either unnecessary or already under review in Fedora. | [[MaryEllenFoster]] has been working on packaging the Java based Sesame2 backend for Nepomuk to replace the Redland backend. Unfortunately, Sesame2 is dependent on many other Java packages which must first be packaged for inclusion in Fedora. There are many packages that still need to be packaged for this backend to make it into Fedora<ref>https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame</ref>. Mary Ellen has been working hard to package many of these dependencies, but this has recently fallen in priorities to personal business. Now that she has more time to put into this packaging,<ref>http://mairi-ruadh.livejournal.com/62989.html</ref> she has realized that many of the packages on her wiki page were either unnecessary or already under review in Fedora. | ||
After Sebastian Trueg announced<ref>http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/</ref> on his blog about getting Soprano and Virtuoso to work together, [[User:Rdieter|Rex Dieter]] began work on packaging the virtuoso backend as virtuoso-opensource. The Soprano plugins will not be stable until the release of KDE4.4 however, Dieter has packaged snapshots with working virtuoso support in the kde-redhat unstable repository<ref>http://kde-redhat.sf.net/</ref> as virtuoso-opensource 5.0.12-1 and soprano 2.3.67-0.1.20091102. After installing these pacakages, follow steps 5-7 outline on Trueg's blog post<ref>http://trueg.wordpress.com/2009/10/22/virtuoso-once-more-with-feeling/<ref> and you should be up and running. Please report any issues to the Fedora-KDE mailing list<ref>https://admin.fedoraproject.org/mailman/listinfo/fedora-kde</ref>. This is, however, extrememly early software, and may have many bugs blocking regular use. | After Sebastian Trueg announced<ref>http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/</ref> on his blog about getting Soprano and Virtuoso to work together, [[User:Rdieter|Rex Dieter]] began work on packaging the virtuoso backend as virtuoso-opensource. The Soprano plugins will not be stable until the release of KDE4.4 however, Dieter has packaged snapshots with working virtuoso support in the kde-redhat unstable repository<ref>http://kde-redhat.sf.net/</ref> as virtuoso-opensource 5.0.12-1 and soprano 2.3.67-0.1.20091102. After installing these pacakages, follow steps 5-7 outline on Trueg's blog post<ref>http://trueg.wordpress.com/2009/10/22/virtuoso-once-more-with-feeling/</ref> and you should be up and running. Please report any issues to the Fedora-KDE mailing list<ref>https://admin.fedoraproject.org/mailman/listinfo/fedora-kde</ref>. This is, however, extrememly early software, and may have many bugs blocking regular use. | ||
<references /> | <references /> | ||
Revision as of 20:37, 16 November 2009
KDE
This section covers the news surrounding the Fedora KDE Special Interests Group[1].
Contributing Writer: Ryan Rix
New Soprano Backends coming to Fedora KDE
MaryEllenFoster has been working on packaging the Java based Sesame2 backend for Nepomuk to replace the Redland backend. Unfortunately, Sesame2 is dependent on many other Java packages which must first be packaged for inclusion in Fedora. There are many packages that still need to be packaged for this backend to make it into Fedora[1]. Mary Ellen has been working hard to package many of these dependencies, but this has recently fallen in priorities to personal business. Now that she has more time to put into this packaging,[2] she has realized that many of the packages on her wiki page were either unnecessary or already under review in Fedora.
After Sebastian Trueg announced[3] on his blog about getting Soprano and Virtuoso to work together, Rex Dieter began work on packaging the virtuoso backend as virtuoso-opensource. The Soprano plugins will not be stable until the release of KDE4.4 however, Dieter has packaged snapshots with working virtuoso support in the kde-redhat unstable repository[4] as virtuoso-opensource 5.0.12-1 and soprano 2.3.67-0.1.20091102. After installing these pacakages, follow steps 5-7 outline on Trueg's blog post[5] and you should be up and running. Please report any issues to the Fedora-KDE mailing list[6]. This is, however, extrememly early software, and may have many bugs blocking regular use.
- ↑ https://fedoraproject.org/wiki/MaryEllenFoster/SopranoSesame
- ↑ http://mairi-ruadh.livejournal.com/62989.html
- ↑ http://trueg.wordpress.com/2009/10/09/virtuoso-for-real/
- ↑ http://kde-redhat.sf.net/
- ↑ http://trueg.wordpress.com/2009/10/22/virtuoso-once-more-with-feeling/
- ↑ https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
gtk-qt-engine retired, replaced with kcm-gtk
User:Rdieter has decided to orphan the gtk-qt-engine package in favor of replacing it with the kcm-gtk package. The packages are for all intents and purposes identical except kcm-gtk doesn't ship the Qt style for gtk.