Re: definitions and package for plasma on meego
On Tuesday 13 July 2010, Aaron J. Seigo wrote: > hi ... > > i (along with some other kde people) are in preliminary discussions with > some companies regarding putting KDE and Plasma on devices. one in > particular is looking at Plasma Netbook + modifications for a tablet > device running MeeGo. > > this kind of opportunity will likely become more frequent, but as they > appear they are usually going to be one time events: we will have one good > shot with each company. > > right now, we're missing a very critical piece of the puzzle which is > preventing these companies from starting to get involved in R&D type > activities with us: > > we need a clear description of what "KDE on MeeGo" is. > > this includes: > > * build instructions for MeeGo i can wipe out my sdk and start a build from scratch, annotating each step one has to do after the chroot is set up to get at least kdelibs and kdebase working. > * tarballs they can download with the relevant sources (could be just a > list of links to existing tarballs we release) yep, that one is easy :) > * lists of files/libraries that end up being installed as part of kdelibs > and runtime on MeeGo uhm, everything, every so, header and so forth? > * documentation of the MeeGo profiles (tablet, mobile) that go into kdelibs do we already have plasma running on a limited profie? > i know these are all "works in progress" type things, but if we have > documentation on them, please speak up and post links so we can pass them > on to the interested parties. > > there is some information here: > > http://techbase.kde.org/Projects/Mobile > > but it's a bit spotty and not something we can hand to a 3rd party, really. > there is also some interesting TODO's here: > > http://techbase.kde.org/Projects/Mobile/PlatformModifications > > and some packaging docs here: > > http://techbase.kde.org/Projects/Mobile/MaemoPackages > > but again, this is more in the category of "internal notes". > > i also have read the notes from the mobile BoF at akademy: > > http://techbase.kde.org/Projects/Mobile/Meetings/Akademy2010#Minutes > > some great stuff there; but it's missing "documentation for 3rd parties". > some may be tempted to say "but we aren't ready for 3rd parties", but > that's incorrect: we are ready for early adopters who are ready and > willing to help out and work with the code alongside us. it's an > opportunity to get more people helping us instead of trying to do it all > on our own like heros with the idea of having something "complete" one day > to offer to 3rd parties. while many 3rd parties are going to want that > "something complete", not everyone needs that and some are going to want > to be involved in making it happen. i fear the time is really tight and we should have stuff ready "for yesterday" something that we really need is a set of meego packages of 4.5, or the current trunk, or whatever. i don't have any knowledge whatsoever about packaging, but is the biggest thing -everyone- interested in it is asking > i don't have the knowledge necessary to put together this kind of > documentation, so i'm asking that those who do can come together and help > me do so. if we can have a working meetng on irc sometime this week to do > so, that would be great, too. i'd like to end up with some basic recipes > on getting the KDE Dev Platform on MeeGo along with a slide presentation > for the technical management, and i'm willing to do a lot of the writing > if we can scrape together the technical information. > > i'm available all of tomorrow and the next day to work on this. who will > help out? i'll be here as well of course :p -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On July 13, 2010, Marco Martin wrote: > > * build instructions for MeeGo > > i can wipe out my sdk and start a build from scratch, annotating each step > one has to do after the chroot is set up to get at least kdelibs and > kdebase working. that would be pure awesome. > > * tarballs they can download with the relevant sources (could be just a > > list of links to existing tarballs we release) > > yep, that one is easy :) > > > * lists of files/libraries that end up being installed as part of kdelibs > > and runtime on MeeGo > > uhm, everything, every so, header and so forth? i don't think we need to worry about headers (that's a development system thing, right?), but just what would end up on a target system. so, libraries, .desktop files, etc. > > * documentation of the MeeGo profiles (tablet, mobile) that go into > > kdelibs > > do we already have plasma running on a limited profie? i did some work along with kevin to make that happen. there is more work to do (e.g. making kio optional in libplasma), but we're getting there. > i fear the time is really tight and we should have stuff ready "for > yesterday" something that we really need is a set of meego packages of > 4.5, or the current trunk, or whatever. yes, but we don't have that. so we need to just document the current state and keep that up to date as we progress. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tuesday 13 July 2010 22:09:39 Marco Martin wrote: > > i fear the time is really tight and we should have stuff ready "for > yesterday" something that we really need is a set of meego packages of > 4.5, or the current trunk, or whatever. > i don't have any knowledge whatsoever about packaging, but is the biggest > thing -everyone- interested in it is asking MeeGo uses the openSUSE build service, doesn't it? So can't we ask our experts from openSUSE for help? Their release is the day after tomorrow so they should have time again :-) And yes please document the steps for setting up kdelibs and base - I don't want to fight through that - there are better ways to spent the spare time. signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tuesday 13 July 2010, Aaron J. Seigo wrote: > On July 13, 2010, Marco Martin wrote: > > > * build instructions for MeeGo > > > > i can wipe out my sdk and start a build from scratch, annotating each > > step one has to do after the chroot is set up to get at least kdelibs > > and kdebase working. > > that would be pure awesome. > > > > * tarballs they can download with the relevant sources (could be just a > > > list of links to existing tarballs we release) > > > > yep, that one is easy :) > > > > > * lists of files/libraries that end up being installed as part of > > > kdelibs and runtime on MeeGo > > > > uhm, everything, every so, header and so forth? > > i don't think we need to worry about headers (that's a development system > thing, right?), but just what would end up on a target system. so, > libraries, .desktop files, etc. horrible (really beyond horrible) checkinstall generated packages could be a start to find out exactly what gets installed and how is big > > > * documentation of the MeeGo profiles (tablet, mobile) that go into > > > kdelibs > > > > do we already have plasma running on a limited profie? > > i did some work along with kevin to make that happen. there is more work to > do (e.g. making kio optional in libplasma), but we're getting there. ok, i can help on this as well > > i fear the time is really tight and we should have stuff ready "for > > yesterday" something that we really need is a set of meego packages of > > 4.5, or the current trunk, or whatever. > > yes, but we don't have that. so we need to just document the current state > and keep that up to date as we progress. yes, this ill make life easier for some future packager (that i hope not too future :p) Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tuesday 13 July 2010, Martin Gräßlin wrote: > On Tuesday 13 July 2010 22:09:39 Marco Martin wrote: > > i fear the time is really tight and we should have stuff ready "for > > yesterday" something that we really need is a set of meego packages of > > 4.5, or the current trunk, or whatever. > > i don't have any knowledge whatsoever about packaging, but is the biggest > > thing -everyone- interested in it is asking > > MeeGo uses the openSUSE build service, doesn't it? So can't we ask our > experts from openSUSE for help? Their release is the day after tomorrow so > they should have time again :-) what would be needed to use the obs would be either the own meego one to be opened (is it already?) or the suse obs to have meego as an available platform to build to > And yes please document the steps for setting up kdelibs and base - I don't > want to fight through that - there are better ways to spent the spare time. last time i tried seemed quite easy, we'll see if it's still so :) -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tue 13 July 2010 3:49:53 pm Aaron J. Seigo wrote: > hi ... > > i (along with some other kde people) are in preliminary discussions with > some companies regarding putting KDE and Plasma on devices. one in > particular is looking at Plasma Netbook + modifications for a tablet > device running MeeGo. > > this kind of opportunity will likely become more frequent, but as they > appear they are usually going to be one time events: we will have one good > shot with each company. > > right now, we're missing a very critical piece of the puzzle which is > preventing these companies from starting to get involved in R&D type > activities with us: > > we need a clear description of what "KDE on MeeGo" is. > > this includes: > > * build instructions for MeeGo > > * tarballs they can download with the relevant sources (could be just a > list of links to existing tarballs we release) > > * lists of files/libraries that end up being installed as part of kdelibs > and runtime on MeeGo > > * documentation of the MeeGo profiles (tablet, mobile) that go into kdelibs > > i know these are all "works in progress" type things, but if we have > documentation on them, please speak up and post links so we can pass them > on to the interested parties. > > there is some information here: > > http://techbase.kde.org/Projects/Mobile > > but it's a bit spotty and not something we can hand to a 3rd party, really. > there is also some interesting TODO's here: > > http://techbase.kde.org/Projects/Mobile/PlatformModifications > > and some packaging docs here: > > http://techbase.kde.org/Projects/Mobile/MaemoPackages > > but again, this is more in the category of "internal notes". > > i also have read the notes from the mobile BoF at akademy: > > http://techbase.kde.org/Projects/Mobile/Meetings/Akademy2010#Minutes > > some great stuff there; but it's missing "documentation for 3rd parties". > some may be tempted to say "but we aren't ready for 3rd parties", but > that's incorrect: we are ready for early adopters who are ready and > willing to help out and work with the code alongside us. it's an > opportunity to get more people helping us instead of trying to do it all > on our own like heros with the idea of having something "complete" one day > to offer to 3rd parties. while many 3rd parties are going to want that > "something complete", not everyone needs that and some are going to want > to be involved in making it happen. > > i don't have the knowledge necessary to put together this kind of > documentation, so i'm asking that those who do can come together and help > me do so. if we can have a working meetng on irc sometime this week to do > so, that would be great, too. i'd like to end up with some basic recipes > on getting the KDE Dev Platform on MeeGo along with a slide presentation > for the technical management, and i'm willing to do a lot of the writing > if we can scrape together the technical information. I plan on doing some heavy investigation/prodding of people to document the full process of building RPMs for MeeGo packages... I have a mostly-working (sic) plasma-mobile-meego package specfile, but yeah, no real guidance on how to do that. I've yet to hear back from Fedora's MeeGo d00dz, so I will go harass other people... Hold me to that please :) > i'm available all of tomorrow and the next day to work on this. who will > help out? *raises his hand slowly* I'll be around as always in irc, etc. Ryan -- Ryan Rix == http://hackersramblings.wordpress.com | http://rix.si/ == == http://rix.si/page/contact/ if you need a word == signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tue, Jul 13, 2010 at 11:09 PM, Marco Martin wrote: > i fear the time is really tight and we should have stuff ready "for yesterday" > something that we really need is a set of meego packages of 4.5, or the > current trunk, or whatever. > i don't have any knowledge whatsoever about packaging, but is the biggest > thing -everyone- interested in it is asking I could do the packaging quickly if you point where are the source I should take. It's part of my daily work (I maintain packages for MeeGo). > what would be needed to use the obs would be either the own meego one to be > opened (is it already?) or the suse obs to have meego as an available platform > to build to MeeGo community OBS is in testing phase. The MeeGo target isn't ready yet. OpenSUSE OBS doesn't have MeeGo target. In the meantime, I could use MeeGo OBS (the closed one) to build the packages. Cheers, Fathi ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Wednesday 14 July 2010, Fathi Boudra wrote: > On Tue, Jul 13, 2010 at 11:09 PM, Marco Martin wrote: > > i fear the time is really tight and we should have stuff ready "for > > yesterday" something that we really need is a set of meego packages of > > 4.5, or the current trunk, or whatever. > > i don't have any knowledge whatsoever about packaging, but is the biggest > > thing -everyone- interested in it is asking > > I could do the packaging quickly if you point where are the source I > should take. dude, that would be awesome! would be a list of the tarball sources ok? and, question for everybody, d we start with the regular full build or directly with a slimmed down version of kdelibs? (not everything builds yet?) > It's part of my daily work (I maintain packages for MeeGo). > > > what would be needed to use the obs would be either the own meego one to > > be opened (is it already?) or the suse obs to have meego as an available > > platform to build to > > MeeGo community OBS is in testing phase. The MeeGo target isn't ready yet. > OpenSUSE OBS doesn't have MeeGo target. > In the meantime, I could use MeeGo OBS (the closed one) to build the > packages. > that would speed up a lot when the community one will be open. all the building blocks would be already there. Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
> would be a list of the tarball sources ok? yeah. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
2010/7/14 Bjoern Ricks : > Imho we should unify the package layout for all mobile platforms. I am not > sure if that is possible with different packaging system but we should give > it a try. Our packages for maemo are already installable and usable on the > N900. But nobody did provide packages for plasma mobile yet. I am not > familiar with rpm packaging yet but I would like to contribute for KDE PIM. +10 on this one. Let's try to use the same packages as most as possible (I know that different projects have different needs and this reflects in the way that kdelibs are compiled - platform profiles). But if we could use almost the same stuff, it would be *wonderful*. The infrastructure that Bjoern already provides is awesome. You just keep doing your job on trunk and the "snapshots" repository give you updated packages every day or so! :D Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On July 14, 2010, Marco Martin wrote: > and, question for everybody, d we start with the regular full build or > directly with a slimmed down version of kdelibs? (not everything builds > yet?) we should start with the slimmed down version of kdelibs, otherwise there's no real point in trying to make them (if we aren't going to use them). finding out what doesn't build will be a great exercise. the biggest challenge is probably going to be handling the difference between "tablet" and "mobile". i'm not sure if MeeGo has the ability to provide different build profiles for different form factors or if it is "one size fits all". if it "one size fits all", then i'd suggest we start with the tablet profile since we probably have immediate use cases for that. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On July 14, 2010, Artur Souza (MoRpHeUz) wrote: > The infrastructure that Bjoern already provides is awesome. You just > keep doing your job on trunk and the "snapshots" repository give you > updated packages every day or so! :D where is this? -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Wed, Jul 14, 2010 at 2:42 PM, Aaron J. Seigo wrote: > where is this? http://files.kolab.org/local/maemo/ Cheers, ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Tuesday 13 July 2010, Aaron J. Seigo wrote: > On July 13, 2010, Marco Martin wrote: > > > * build instructions for MeeGo > > > > i can wipe out my sdk and start a build from scratch, annotating each > > step one has to do after the chroot is set up to get at least kdelibs > > and kdebase working. > > that would be pure awesome. this is a first rough draft of a sdk install guide. there should be enough information to be able to follow it and have a kde built and installed. it's done with the cmakekde scripts to have to explain the minimum amount possible, should be easy to adapt to a manual cmake by hand guide. it builds the full kde profile with the minimum amount possible of dependencies to barely build (maybe could be worth enabling dependencies for remote applets in the future) the good news is that almost everything needed is already packaged in meego with the exceptions of: mysql sqlite (too old) dbusmenu-qt will have to be adapted to the other profiles as well. i will now put it on techbase Cheers, Marco Martin Build and install KDE in a MeeGo chroot environment. 1) setup a chroot environment as described in the MeeGo wiki page http://wiki.meego.com/Getting_started_with_the_MeeGo_SDK_for_Linux 2) modify the ~/.bashrc script as described at the KDE wiki page http://techbase.kde.org/Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc 3) execute the following command (needed only the first time, not subsequent restarts) source ~/.bashrc 3) Once entered in the MeeGo chroot environment, setup the KDE build environment. 4) Install the following required packages with yum for basic development (any dependency will be automatically installed by yum) yum install packagename (as root) - required for all: svn cmake git rpm-devel There are two packages that needs to be built before kdesupport. MySql, because is not present in the MeeGo repositories and SqlLite, because the shipped version is too old. Setup Mysql: - Download the source RPM from http://dev.mysql.com/downloads/mysql/ select Source code, Generic Linux - su root - execute rpm -i MySQL-5.1.48-1.glibc23.src.rpm - cd ~/rpmbuild/SPECS - rpmbuild -dd mysql.spec - cd ~/rpmbuild/RPMS/i386 - rpm -Uvh MySQL-devel-5.1.48-1.glibc23.i386.rpm MySQL-server-5.1.48-1.glibc23.i386.rpm Setup Sqlite: - Download http://sqlite.org/sqlite-amalgamation-3.6.23.1.tar.gz - tar xzvf sqlite-amalgamation-3.6.23.1.tar.gz - cd sqlite-3.6.23.1 - ./configure --prefix=/usr - make - (as root) make install -required for kdesupport: boost-devel sqlite-devel bzip2-devel libxml2-devel dbus-devel raptor-devel redland-devel qca2-devel -required by Phonon: pulseaudio-devel libxcb-devel gstreamer-devel gst-plugins-base-devel -required by kdelibs: pcre-devel qjson-devel giflib-devel libxslt-devel docbook-style-xsl NOTE: In order to work properly, nepomuk would need a manually built Virtuoso server, but is not required for the build tough. FIXME: cmakekde appears to require makeobj from kdesdk, that's a bit weird dependency. -required by kdepimlibs: libical-devel gpgme-devel cyrus-sasl-devel -required by kdebase: libxkbfile-devel libXcomposite-devel libXdamage-devel libXau-devel -required by kdeplasma-addons libXtst-devel scim-devel (only if the scim widget is needed) 5) prepare a folder for checkout and development - su meego - cd - mkdir kde - cd kde - mkdir src - mkdir build - cd src - mkdir trunk - cd trunk 6) Download the kdesupport libraries - svn co svn://anonsvn.kde.org/home/kde/trunk/kdesupport - execute the command (bash alias) "cb" - cmakekde 7) Download a recent copy of Phonon - cd - mkdir git - cd git - git clone git://gitorious.org/phonon/phonon.git - cd phonon - mkdir build - cd build - cmake .. -DCMAKE_INSTALL_PREFIX=/usr - make - make install (as root) 8) Download Dbusmenu-qt - cd ~git - git clone git://gitorious.org/dbusmenu/dbusmenu-qt.git - cd dbusmenu-qt - mkdir build - cmake .. -DCMAKE_INSTALL_PREFIX=/usr - make - make install (as root) 9) Download the whole KDE SC - cs - svn co svn://anonsvn.kde.org/home/kde/trunk/KDE 10) Build kdelibs - cb - cd kdelibs - cmakekde 11) Build kdepimlibs - cb - cd kdepimlibs - cmakekde 12) Build kdebase - cb - cd kdebase - cmakekde 13) Build kdeplasma-addons - cb - cd kdeplasma-addons - cmakekde ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On July 15, 2010, Marco Martin wrote: > this is a first rough draft of a sdk install guide. > there should be enough information to be able to follow it and have a kde > built and installed. great start; we should put this on techbase.kde.org, perhaps under /Projects/Plasma until we have something we can move to Getting Started. also, i wonder if we couldn't create a shell script to do the KDE bits... perhaps a "first run" script that alters the .bashrc (maybe create a .kdebashrc file that is included from .bashrc, to keep it all simpler and easier to back out?), that checks out the relevant source code (checking out the entire SC is a bit much, perhaps just support/libs/base/plasma-addons? it could also grab phonon and dbusmenu-qt) and does step 5. that should automate steps 5-9 pretty much. then it's just 10-12 with 13 being optional. thoughts? -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Thursday 15 July 2010, Aaron J. Seigo wrote: > On July 15, 2010, Marco Martin wrote: > > this is a first rough draft of a sdk install guide. > > there should be enough information to be able to follow it and have a kde > > built and installed. > > great start; we should put this on techbase.kde.org, perhaps under > /Projects/Plasma until we have something we can move to Getting Started. i did just putted in into http://techbase.kde.org/Projects/Mobile/build_on_MeeGo i can move it back to plasma if it's better > also, i wonder if we couldn't create a shell script to do the KDE bits... > perhaps a "first run" script that alters the .bashrc (maybe create a > .kdebashrc file that is included from .bashrc, to keep it all simpler and > easier to back out?), that checks out the relevant source code (checking > out the entire SC is a bit much, perhaps just > support/libs/base/plasma-addons? it could also grab phonon and > dbusmenu-qt) and does step 5. > > that should automate steps 5-9 pretty much. > > then it's just 10-12 with 13 being optional. > > thoughts? yes, a little script could be handy Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On July 15, 2010, Marco Martin wrote: > On Thursday 15 July 2010, Aaron J. Seigo wrote: > > On July 15, 2010, Marco Martin wrote: > > > this is a first rough draft of a sdk install guide. > > > there should be enough information to be able to follow it and have a > > > kde built and installed. > > > > great start; we should put this on techbase.kde.org, perhaps under > > /Projects/Plasma until we have something we can move to Getting Started. > > i did just putted in into > http://techbase.kde.org/Projects/Mobile/build_on_MeeGo > i can move it back to plasma if it's better no, that's fine :) great start.. thanks.. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
> sqlite (too old) sqlite 3.6.22 too old ? sqlite 3.6.23.1 is the latest released version. I'll ask an update. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Fri, Jul 16, 2010 at 11:34 AM, Fathi Boudra wrote: >> sqlite (too old) > > sqlite 3.6.22 too old ? > sqlite 3.6.23.1 is the latest released version. > I'll ask an update. yup, apparently something requires 3.6.23, don't know exactly the reason Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego
On Wednesday 14 July 2010 19:42:06 Aaron J. Seigo wrote: > the biggest challenge is probably going to be handling the difference > between "tablet" and "mobile". i'm not sure if MeeGo has the ability to > provide different build profiles for different form factors or if it is > "one size fits all". if it "one size fits all", then i'd suggest we start > with the tablet profile since we probably have immediate use cases for > that. Note that with the current state though there's no practical difference between the tablet and mobile profile (yet!). But for those who attended my talk at Akademy, latest plans are to converge to having no profiles at all in the end with "automagic" runtime dependency checks. That's why I would kind of advise people to use the mobile profile at that point when they don't build the desktop one. That'll also help us analyze better the trade off of having a given dependency missing or not. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud patron of KDE, http://www.kdab.com signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego (Fathi Boudra)
> > > sqlite (too old) > > sqlite 3.6.22 too old ? > sqlite 3.6.23.1 is the latest released version. > I'll ask an update. > ..and for Nepomuk a quad store like Virtuoso? :-) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: definitions and package for plasma on meego (Fathi Boudra)
On Friday 16 July 2010, PierreL wrote: > > > sqlite (too old) > > > > sqlite 3.6.22 too old ? > > sqlite 3.6.23.1 is the latest released version. > > I'll ask an update. > > ..and for Nepomuk a quad store like Virtuoso? :-) > yeah, probably here the only ones that can really answer what is really needed are the kdepim mobile guys. at the moment, in order for akonady working well, both mysql and virtuoso are needed. i did hear some time ago plans about using just virtuoso also in place of mysql but i have no idea if it has been declared a feasible path or not ;) Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
