Re: Another proposal for modernization of our infrastructure

On Saturday, January 31, 2015 20:52:44 Eike Hein wrote: > On 01/31/2015 08:37 PM, Christoph Feck wrote: > > Excuse me, but if KDE developers will have to follow equivalent steps > > as described at http://qt-project.org/wiki/Setting-up-Gerrit to > > contribute, then I predict another big loss of de

Re: Another proposal for modernization of our infrastructure

On Saturday, January 31, 2015 21:11:19 Eike Hein wrote: > On 01/31/2015 08:57 PM, Alexander Neundorf wrote: > > hmm, looking back at our switch to git, I don't consider our standards for > > documentation of the developer workflow as very high unfortunately. :-/ > &g

Re: Another proposal for modernization of our infrastructure

On Saturday, January 31, 2015 22:52:22 Andreas Pakulat wrote: > Hi, > > just a short note (don't want this to become a complete subthread > distracting from the actual proposal-discussion) > > On Sat, Jan 31, 2015 at 9:38 PM, Alexander Neundorf > > wrote: >

Re: Distros and QtWebEngine

On Monday, April 20, 2015 22:54:26 Thomas Lübking wrote: > On Montag, 20. April 2015 22:31:24 CEST, Jeremy Whiting wrote: > > Even simple applications may want to use a webview for stuff. Kanagram at > > one point had a QtWebkit Web view just to show the wikipedia entry of the > > current word. >

Re: Naming scheme for Qt5/KF5-based libraries outside of KF5

On Sunday, September 27, 2015 17:21:04 Sune Vuorela wrote: > On 2015-09-27, Boudhayan Gupta wrote: > > What I propose is that all libraries which want to manage their own > > release cycles and their own namespaces, be moved to Extragear Libs > > and release from there. All the libraries which can

Re: State of Audio CD support in KDE

On Wednesday, September 30, 2015 05:33:20 Boudhayan Gupta wrote: > Hi Albert (and others), > > On 30 September 2015 at 04:09, Albert Astals Cid wrote: > >> In terms of support for Audio CDs in KDE, > >> > >> * K3B can write them. > >> * Phonon the API can play them, with some minor but weird bug

Re: State of Audio CD support in KDE

On Friday, October 02, 2015 04:46:08 Boudhayan Gupta wrote: > On 2 October 2015 at 01:19, Albert Astals Cid wrote: > > I'd miss the ripping habilities of kio-audiocd personally, maybe we can > > merge it with kaudiocreator and make them share code? > > Yeah, let's make KAudioCreator do the conver

How to commit to kruler ?

Hi, it seems to me that kruler is basically unmaintained, e.g. the patch for bug https://bugs.kde.org/show_bug.cgi?id=317436 hasn't been applied since April 2013. So, I'd like to fix that now. How is the procedure for kruler ? Do I need to post this to Phabricator for review first ? (I don't exp

Re: What's kde-core-devel for?

On 2016 M12 19, Mon 10:24:29 CET Jan Kundrát wrote: > KDE has expanded over the last few years to include projects which are not > based on kdelibs or kf5 (or even Qt). I have heard that several times. Which are those beside Wiki2Learn ? Alex

Re: What's kde-core-devel for?

On 2016 M12 19, Mon 22:48:29 CET Albert Astals Cid wrote: ... > Please let's try to stay focused on topic. > > Cheers, > Albert > > P.S: took me like 4 minutes > > PHP- https://cgit.kde.org/websites/capacity.git/ > Java - https://cgit.kde.org/kdeconnect-android.git/ > Python - https://we

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 5, Thu 16:11:43 CET Kevin Kofler wrote: > Ben Cooksley wrote: > > On Thu, Jan 5, 2017 at 10:28 PM, Martin Gräßlin wrote: > >> It should be rather obvious that we don't introduce new dependencies > >> because we like to. There is a very important software reason to it. > >> That's the ca

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 6, Fri 22:39:22 CET Ben Cooksley wrote: > See my notes above re. why tying this to the dependency freeze date is > a bad idea and won't really work. > > Given that we potentially have to take into account Qt version bumps > and base system rebuilds - i'll give a timeline of 1 month's a

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 6, Fri 17:20:08 CET Kevin Kofler wrote: > PS: > > I wrote: > > Martin Gräßlin wrote: > >> For packagers it should not matter at all. This is the most common > >> situation for distribution. And in the release of e.g. Plasma they have > >> to handle this for hundreds of updated dependen

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 12, Thu 04:00:34 CET Kevin Kofler wrote: > Martin Gräßlin wrote: > > Email threads don't work to codify such requirements. What we need is > > something like an "announce new dependency to sysadmin freeze" prior to > > the dependency freeze in the release schedule. That's what I mean wi

Re: CI Requirements - Lessons Not Learnt?

Hi Martin, just replying somewhere... On 2017 M01 15, Sun 14:52:30 CET Martin Gräßlin wrote: > I think that is a reasonable suggestion. If distros patch our > dependencies we need to consider this as a fork. And a fork should be > called a fork. It needs to be clear that KDE is not responsible fo

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 16, Mon 07:48:25 CET Martin Gräßlin wrote: > Am 2017-01-15 22:58, schrieb Alexander Neundorf: > > Hi Martin, > > > > just replying somewhere... > > > > On 2017 M01 15, Sun 14:52:30 CET Martin Gräßlin wrote: > >> I think that is a r

Re: CI Requirements - Lessons Not Learnt?

On 2017 M01 18, Wed 19:59:46 CET Friedrich W. H. Kossebau wrote: .. > Given this is a policy affecting all of the KDE projects, please first > propose it officially in a separate own thread, with a proper subject. > Perhaps even on kde-community, as kde-core-devel might not be read by many, > give

Re: liquidshell in kdereview

On 2017 M11 3, Fri 21:30:19 CET Martin Koller wrote: > Hi all, ... > - Just one bottom DesktopPanel, containing: I always put my panel to the right or left edge (intead at the bottom)... ... > The main motivation was to have a reliable desktop shell which does not hog > the CPU or RAM. (CPU usage

Re: liquidshell in kdereview

On 2017 M11 5, Sun 19:27:27 CET Martin Koller wrote: > On Samstag, 4. November 2017 20:58:49 CET Alexander Neundorf wrote: > > On 2017 M11 3, Fri 21:30:19 CET Martin Koller wrote: > > > Hi all, > > > > ... > > > > > - Just one bottom DesktopPanel,

Re: liquidshell in kdereview

On 2017 M11 6, Mon 19:13:36 CET Martin Koller wrote: > On Montag, 6. November 2017 10:03:05 CET Tomaz Canabrava wrote: > > On Mon, Nov 6, 2017 at 8:31 AM, Martin Koller wrote: > > > On Montag, 6. November 2017 01:57:32 CET Aleix Pol wrote: > > > > On Fri, Nov 3, 2017 at 9:30 PM, Martin Koller wro

Re: liquidshell in kdereview

On 2017 M11 6, Mon 10:03:05 CET Tomaz Canabrava wrote: > On Mon, Nov 6, 2017 at 8:31 AM, Martin Koller wrote: ... > > Whoever does not like plasmashell, for whatever reason. > > My reasons are mentioned in the README or the announcement mail. > > Free software is about choice, no ? > > It is, of

Re: CI system maintainability

On 2019 M03 28, Thu 17:43:36 CET Friedrich W. H. Kossebau wrote: ... > Though I assume no-one is using it anyway, given there are so few bugs > reported ;) I use it whenever I need to look at a file "raw", and I can't remember having noticed bugs :-) Alex

Re: CI system maintainability

Hi, On 2019 M03 28, Thu 16:04:01 CET Boudhayan Gupta wrote: > Hi, > > On Thu, 28 Mar 2019 at 15:21, Kevin Ottens wrote: > > Hello, > > > > On Thursday, 28 March 2019 14:33:59 CET laurent Montel wrote: > > > I am against to force mandatory review, as it will create a lot of lose > > > > of > >

Re: KF5 Update Meeting Minutes 2013-w35

On Tuesday 27 August 2013, Kevin Ottens wrote: > Hello everyone, > > This is the minutes of the Week 35 KF5 meeting. As usual it has been held > on #kde-devel at 4pm Paris time. > > Were present: afiestas, apol, d_ed, dfaure, mck182, mgraesslin, sebas, > shadeslayer, teo, vHanda, wojtask9 and mys

Re: Regression in CMake breaking builds

On Sunday 15 September 2013, Ben Cooksley wrote: > Hi all, > > It appears that a recent update to CMake on build.kde.org has broken a > number of KDE projects, resulting in them now failing to build. > > An example can be found here: > http://build.kde.org/view/FAILED/job/kdevplatform_master/560/

Re: Regression in CMake breaking builds

On Sunday 15 September 2013, Ben Cooksley wrote: > On Sun, Sep 15, 2013 at 10:52 PM, Alexander Neundorf wrote: > > On Sunday 15 September 2013, Ben Cooksley wrote: > >> Hi all, > >> > >> It appears that a recent update to CMake on build.kde.org has

Re: Packaging KDE Foundation 5 frameworks

On Wednesday 09 October 2013, Lubomir Rintel wrote: > Hi, > > I know it's a bit too early, but still better than late. I'd like to > know your thoughts about the way KF5 frameworks will be packaged for > Linux distributions. > > I'm currently working on including Hawaii desktop (based around a Qt

Re: Packaging KDE Foundation 5 frameworks

On Thursday 10 October 2013, Milian Wolff wrote: > On Wednesday 09 October 2013 19:26:48 Alexander Neundorf wrote: > > On Wednesday 09 October 2013, Lubomir Rintel wrote: > > > Hi, > > > > > > I know it's a bit too early, but still better than late. I

Re: KF5 Update Meeting Minutes 2013-w42

On Tuesday 15 October 2013, Kevin Ottens wrote: > Hello everyone, .. > * steveire recommends _LIBRARIES variables from Config files and the > template, Is there a verb missing in this sentence ? Alex

Re: Dependency to unreleased versions

On Sunday 20 October 2013, Torgny Nyblom wrote: > Hi, > > What is the policy of depending on unreleased libraries? And is that > written down somewhere? > > Reason I'm asking is this commit > http://build.kde.org/view/FAILED/job/libkdcraw_master/83/changes#detail1 > > It introduces a dependency

Re: FindKDE4Internal.cmake & clang & c++11 & -fdelayed-template-parsing

On Friday 15 November 2013, Milian Wolff wrote: > On Tuesday 22 October 2013 10:17:02 Raphael Kubo da Costa wrote: > > Milian Wolff writes: > > > Hey Raphael! > > > > > > Thank you for working on clang support in FindKDE4Internal.cmake. > > > > > > Since recently though I have build issues with

Less time for KDE... :-)

Hi, for very happy personal reasons (since Tuesday, named David :-) ) I'll have significantly less time for KDE in the future. Still I'll stick around and try my best. Alex P.S. no, it is not because of dfaure ;-)

Re: KMountPoint::probablySlow and cifs mount points

On Monday 25 November 2013, Aurélien Gâteau wrote: > Le lundi 25 novembre 2013 13:54:38 Mark Gaiser a écrit : > > On Mon, Nov 25, 2013 at 10:45 AM, Aurélien Gâteau wrote: > > > Le dimanche 24 novembre 2013 19:42:25 Mark Gaiser a écrit : ... > > >> What should be done is detecting is the target is

Re: KMountPoint::probablySlow and cifs mount points

On Tuesday 26 November 2013, Thomas Lübking wrote: > On Montag, 25. November 2013 23:31:59 CEST, Alexander Neundorf wrote: > > hmm, doesn't have to be really complicated, just a little bit more > > sophisticated than it is now, e.g. like the following, which is > &

Re: Less time for KDE... :-)

On Saturday 23 November 2013, Alexander Neundorf wrote: > Hi, > > for very happy personal reasons (since Tuesday, named David :-) ) I'll have > significantly less time for KDE in the future. > Still I'll stick around and try my best. > > Alex > > P.S. no, it

Re: Nepomuk in 4.13 and beyond

On Thursday 12 December 2013, Ignacio Serantes wrote: > Welcome Baloo, > > New suggestions about development direction to avoid some problems related > to Nepomuk: > > 1) Baloo must work as a service to share information with other users and > minimize resources consumption. With Nepomuk a login

Re: [kdesrc-build] /: Add kate to kdesrc-build's kf5 file.

On Wednesday 01 January 2014, David Faure wrote: > Git commit f878d229011a8fe673329c44382bd8a43644e595 by David Faure. > Committed on 01/01/2014 at 10:00. > Pushed by dfaure into branch 'master'. > > Add kate to kdesrc-build's kf5 file. > > Try to split up the file internally into 3 sections: > f

Re: KDE Frameworks: Moving toward 5.0 final and Governance

On Monday 06 January 2014, Kevin Ottens wrote: > Hello all, > > Now that TP1 is almost out of the door, it is time to move toward the final > release and put in place the governance of KDE Frameworks. It is a very > large and multi-faceted product, so we will need people with longer term > commitm

Re: Co-installability

On Tuesday, April 29, 2014 21:00:57 Christoph Feck wrote: > I cannot remember we had these issues with the KDE3->KDE4 transition. Actually I think we had the same issues. Vaing said that, especially now with frameworks part of the plan is to make it easy to use just some libraries e.g. in an othe

Re: KDE Frameworks Release Cycle

On Sunday, May 04, 2014 16:27:44 Luigi Toscano wrote: > Kevin Ottens ha scritto: > > So, we had a team discussion here with Albert, Aleix, Alex, Alex, > > Aurélien, > > David, Rohan and myself. We juggled with several options, trying to > > address > > > > the following constraints: > > * We don'

Re: Using Gerrit for code review in KDE

On Tuesday, September 09, 2014 20:02:55 Aaron J. Seigo wrote: > On Tuesday, September 9, 2014 18.49:24 Kevin Ottens wrote: > > > As it stands with plasma-framework in particular, there is now a > > > difference > > > in workflow depending on what *part* of plasma one is working on > > > (framework

Re: KF 5.3.0 changelog

Hi, On Monday, October 06, 2014 23:14:33 David Faure wrote: > Dear workspace and application developers, > > In case you're not reading kde-announce, here's the list of changes in > KF 5.3.0, just released. I also read https://dot.kde.org/2014/10/07/third-release-kde-frameworks-brings-multitud

Re: KF 5.3.0 changelog

On Tuesday, October 07, 2014 21:47:07 Albert Astals Cid wrote: > El Dimarts, 7 d'octubre de 2014, a les 21:40:41, Alexander Neundorf va > > escriure: > > Hi, > > > > On Monday, October 06, 2014 23:14:33 David Faure wrote: > > > Dear workspace and app

Re: KF 5.3.0 changelog

On Tuesday, October 07, 2014 22:32:43 Alexander Neundorf wrote: > On Tuesday, October 07, 2014 21:47:07 Albert Astals Cid wrote: > > El Dimarts, 7 d'octubre de 2014, a les 21:40:41, Alexander Neundorf va > > > > escriure: > > > Hi, > > > > >

Re: Triggering rebuild after changing a *.json file

On Sunday, November 23, 2014 23:37:45 Kevin Funk wrote: > On Sunday 23 November 2014 17:54:21 Milian Wolff wrote: > > On Sunday 23 November 2014 10:39:02 Andreas Pakulat wrote: > > > Hi, > > > > > > On Sun, Nov 23, 2014 at 4:36 AM, Milian Wolff wrote: > > > > Hey all, > > > > > > > > in my quest

Re: Changes to our Git infrastructure

On Monday, January 05, 2015 16:15:09 Ian Wadham wrote: ... > I wonder also how many people have just tiptoed quietly away from the KDE > Community rather than speak out about frustrations they may have been > feeling. Where *did* all those people go in the last few years? And why? I didn't reall

Re: Changes to our Git infrastructure

On Monday, January 05, 2015 22:35:23 Albert Astals Cid wrote: > El Dilluns, 5 de gener de 2015, a les 22:22:19, Boudewijn Rempt va escriure: ... > > * figured out what branches are for, and how different projects handle > > those > > Right, that's hardly documentable though (and will get old soon

Re: Changes to our Git infrastructure

On Monday, January 05, 2015 23:53:02 Boudewijn Rempt wrote: > I'm just trying to make clear that reviewboard is a crappy tool inciting > people to write crappy reviews that drive people away. Apart from any > other nonsense about cultural differences (the standard cop-out from > Dutchmen and German

Re: Changes to our Git infrastructure

On Wednesday, January 07, 2015 08:03:06 Martin Gräßlin wrote: > On Tuesday 06 January 2015 12:48:41 Jan Kundrát wrote: > > On Tuesday, 6 January 2015 07:40:01 CEST, Ian Wadham wrote: ... > > This has a risk of splitting the discussion about a patch into multiple > > independent streams where people

Re: New cmake warning.

On Dienstag, 3. Mai 2022 18:43:48 CEST Méven wrote: > Le mar. 3 mai 2022 à 18:25, Thomas Friedrichsmeier < > > thomas.friedrichsme...@kdemail.net> a écrit : > > On Tue, 3 May 2022 10:35:20 +0200 > > > > Méven wrote: > > > I am guessing you are using cmake >= 3.16 so it allows you to run, but > >

Re: Cleaning up cdash.org integration, what to do, or any hidden usage still?

Hi, On Freitag, 2. September 2022 12:20:50 CEST Friedrich W. H. Kossebau wrote: > Hi, > > (cc: kde-devel for heads-up, please reply only to kde-core-devel). > > we stumbled over some CTestConfig.cmake files in some of the KDE git > repositories. Which seem to originate from a time where people w

Re: Kandalf: request for review

On Montag, 18. Dezember 2023 05:06:08 CET J. Varela wrote: > I like that. The k makes sense there. It also fits with the theme of the > target uses. Really ? A Kamel is a big, slow and un-funny animal, in german it's also not a compliment to call somebody a Kamel. Alex

Re: Kandalf: request for review

On Dienstag, 19. Dezember 2023 08:31:56 CET Ingo Klöcker wrote: > On Montag, 18. Dezember 2023 23:30:57 CET jvap...@gmail.com wrote: > > On Montag, 18. Dezember 2023 22:27:43 CET Alexander Neundorf wrote: > > > A Kamel is a big, slow and un-funny animal, in german it's also

Ready-to-use Docker images for KF6-based development ?

Hi, I'm still running a Qt5/KF5-based setup on my machine. Is there a ready-to-use docker image/Dockerfile which I could use to work on a KF6-based application, maybe something from KDE neon ? Sorry for the maybe stupid question Alex

Re: Ready-to-use Docker images for KF6-based development ?

Hi, On Dienstag, 30. Januar 2024 12:53:32 CET Jonathan Riddell wrote: > *Sure, the Neon unstable one should be ready to go* > *invent-registry.kde.org/neon/docker-images/plasma:unstable > * a few days ago it was working today I go

Re: kdewebkit fails to build with Mobile profile in trunk

On Sunday 26 December 2010, Andriy Rysin wrote: > Commenting out two deprecated methods helped but that's probably a wrong > solution. We really do need reliable nightly and/or continuous builds if we seriously want to support the different profiles and platforms. I have a dashboard for each KDE

Please test: [CMake] CMake 2.8.4-rc1 ready for testing!

Hi, CMake is nearing its 2.8.4 release, and a first release candidate is available. This version has a change which may affect the build of KDE, current KDE trunk, and it needs a special command line argument for KDE 4.5.0/4.5.1. Maybe you remember that in the KDE 4.5 cycle there was for a sho

KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

Hi, now that it's getting serious, can somebody who is working on the git migration, *please* take care and write proper documentation on techbase.kde.org for git dummies ? http://techbase.kde.org/Development/Tutorials/Git , which is the first google result, and looks like a gateway page, has

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

On Thursday 20 January 2011, Tom Albers wrote: > - Original Message - > > > On Wed, Jan 19, 2011 at 03:33:30PM -0600, Ian Monroe wrote: > > > There is no push/merge/branching policy for KDE. Different projects > > > will likely do their own thing. For the time being its just the > > > SVN-s

Re: KDE git docs for dummies ? WAS: Re: splitting up kdebase in git

On Thursday 20 January 2011, Aaron J. Seigo wrote: > On Wednesday, January 19, 2011, Alexander Neundorf wrote: > > http://community.kde.org/Sysadmin/GitKdeOrgManual looks quite ok for > > somebody who knows how to use git for KDE, but not for me. > > Can somebody please add

Re: Please test: [CMake] CMake 2.8.4-rc1 ready for testing!

On Saturday 29 January 2011, Christophe Giboudeaux wrote: > Hi, > > On Tuesday 18 January 2011 21:58:24 Alexander Neundorf wrote: > > So please, give this release candidate a good try, and let me know if > > something fails. > > Quick feedback. Thanks for finally turni

Re: proposal: remove KTextEditor interface from kdelibs repository

On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote: > Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit: > > On 2011-02-01, Friedrich W. H. Kossebau wrote: > > > Uh, that is old-fashioned. Should instead ask the user whether she > > > wants to install the proper text editor module.

Re: proposal: remove KTextEditor interface from kdelibs repository

On Tuesday 01 February 2011, Kevin Krammer wrote: > On Tuesday, 2011-02-01, Christoph Cullmann wrote: ... > > Yeah, and because of this requirement, which I can agree on, I didn't > > remove it from kdelibs, as its public API and I wanted to be SC + BC. And > > no, runtime components moving to othe

Re: Initial support for kde_projects.xml in kdesrc-build

On Monday 31 January 2011, Aaron J. Seigo wrote: > On Sunday, January 30, 2011, Michael Pyne wrote: > > Like I said, "xml-support" branch on kdesrc-build git. If you want to > > give > > _very_ cool. will the good news today never end? ;) > > serious question: once this is stabilized, can we make t

Re: proposal: remove KTextEditor interface from kdelibs repository

On Tuesday 01 February 2011, Aaron J. Seigo wrote: > On Monday, January 31, 2011, Andreas Pakulat wrote: > > On 01.02.11 01:18:58, Pino Toscano wrote: > > > Alle martedì 1 febbraio 2011, Aaron J. Seigo ha scritto: > > > > > The concern that I have, on the other hand, is whether this can be > > > >

Re: Merge or Cherry-Pick?

On Monday 31 January 2011, Andreas Pakulat wrote: > Hi, > > something that hasn't been written down as far as I can see (if I > overlooked it, please point me to it) is what the policy on kdelibs is > to be now wrt. merging vs. cherry-picking of changes in branches and > master? > > Andreas Not r

Re: proposal: remove KTextEditor interface from kdelibs repository

On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote: > Mardi, le 1 février 2011, à 19:42, Alexander Neundorf a écrit: > > On Tuesday 01 February 2011, Friedrich W. H. Kossebau wrote: > > > Mardi, le 1 février 2011, à 18:53, Sune Vuorela a écrit: > > > >

Re: Initial support for kde_projects.xml in kdesrc-build

On Tuesday 01 February 2011, Michael Jansen wrote: > On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote: > > On Monday 31 January 2011, Aaron J. Seigo wrote: > > > On Sunday, January 30, 2011, Michael Pyne wrote: > > > > Like I said, "xml-support"

Re: proposal: remove KTextEditor interface from kdelibs repository

On Tuesday 01 February 2011, Andreas Pakulat wrote: > On 01.02.11 19:49:10, Albert Astals Cid wrote: > > A Dimarts, 1 de febrer de 2011, Ian Monroe va escriure: > > > On Mon, Jan 31, 2011 at 21:19, Aaron J. Seigo wrote: > > > >[snip] > > > > > > > > oh well, KTextEditor isn't an option, > > > > >

Re: Initial support for kde_projects.xml in kdesrc-build

On Tuesday 01 February 2011, Michael Jansen wrote: > On Tuesday 01 February 2011 20:35:27 Alexander Neundorf wrote: > > On Tuesday 01 February 2011, Michael Jansen wrote: > > > On Tuesday 01 February 2011 19:53:40 Alexander Neundorf wrote: > > > > On Monday 31 Janu

Re: Initial support for kde_projects.xml in kdesrc-build

On Tuesday 01 February 2011, Michael Jansen wrote: ... > > > kdesupport? anyone ... perhaps qt from trunk or qtsoftware to get > > > problems as early as possible? > > > > I was asking specifically about "KDE" stuff, i.e. everything starting > > with kdelibs, not stuff kdelibs depends on (which I a

Re: Initial support for kde_projects.xml in kdesrc-build

On Tuesday 01 February 2011, Michael Jansen wrote: > > If you find the place let me know. > > No ... only if i am unable to fix it myself :)) . > > > > > Do you need that for running ? > > > > For building it's not necessary. Use CMAKE_PREFIX_PATH. > > > > > > I always thought that PATH controls wh

Re: Initial support for kde_projects.xml in kdesrc-build

On Wednesday 02 February 2011, Michael Pyne wrote: ... > e.g. worrying about environment variables like PKG_CONFIG_PATH is no idle > claim (kdesrc-build sets that as well), along with PATH in order to pick up > the right Qt version. Please try to use only CMAKE_PREFIX_PATH instead of setting PATH.

Re: Merge or Cherry-Pick?

On Wednesday 02 February 2011, Thiago Macieira wrote: > Em quarta-feira, 2 de fevereiro de 2011, às 11:46:20, Wolfgang Rohdewald > > escreveu: > > On Dienstag 01 Februar 2011, Thiago Macieira wrote: > > > > That's not always true. Some changes will be specific to > > > > 4.6, because sections of co

Re: Merge or Cherry-Pick?

On Wednesday 02 February 2011, Oswald Buddenhagen wrote: > On Wed, Feb 02, 2011 at 01:21:44AM -0500, Dawit Alemayehu wrote: > > On Wed, Feb 2, 2011 at 12:58 AM, John Tapsell wrote: > > >> But how would a similar work flow except there are multiple fixes > > > > > > Does that make sense? > > > > Ye

Re: Merge or Cherry-Pick?

On Wednesday 02 February 2011, John Layt wrote: > On Wednesday 02 February 2011 13:43:04 Parker Coates wrote: > > My preferred workflow is to put all local commits intended for master > > in a single, local, long-lived "workmaster" branch instead of putting > > them in master directly. Since the ch

Re: irc meeting for kdelibs git workflow

On Wednesday 02 February 2011, Oswald Buddenhagen wrote: > On Tue, Feb 01, 2011 at 01:37:26PM -0800, Aaron J. Seigo wrote: > > * adapting http://techbase.kde.org/Policies/SVN_Commit_Policy > > i'd suggest a look at http://qt.gitorious.org/qt/pages/CommitPolicy, in > particular point 8 of the rules.

Re: irc meeting for kdelibs git workflow

On Tuesday 01 February 2011, Aaron J. Seigo wrote: > hi everyone ... > > with git having finally arrived more-or-less, we find ourselves without a > well defined work flow for kdelibs (and by extension other KDE > repositories) > > i don't think we can or should hope and pray that our sysadmins wil

Re: irc meeting for kdelibs git workflow

On Wednesday 02 February 2011, Aaron J. Seigo wrote: > On Wednesday, February 2, 2011, Alexander Neundorf wrote: > > * for any change, create a topic branch from master > > * work in the branch... > > in cmake development, how do developers find each other's branc

Re: Keyboard shortcuts get wild.

On Saturday 05 February 2011, Mark wrote: > Hi, > > let me first point you to this image (kde 4.6.0) : > http://img89.imageshack.us/img89/5398/rightmousebuttondesktop.png > > Oke, first one shortcut in that image. > I consider myself a experienced computer user in both windows and linux but > today

Re: Merge or Cherry-Pick?

On Monday 07 February 2011, Andras Mantia wrote: > On Wednesday, February 02, 2011 18:36:28 Alexander Neundorf wrote: > > I don't really care how it will be, but I really think we should agree > > on one common recommended and documented workflow to use. > > I agree of h

Re: [Kde-scm-interest] Re: Usage of pull rebasing and merges

On Tuesday 08 February 2011, Boudewijn Rempt wrote: > On Tuesday 08 February 2011, Oswald Buddenhagen wrote: > > > - just throw away the merge with git reset --hard HEAD~1 and redo it > > > after git pull-ing. preferably, you should have git rerere enabled, > > > so you won't have to repeat res

Re: proposal: remove KTextEditor interface from kdelibs repository

On Wednesday 09 February 2011, Stephen Kelly wrote: > Aaron J. Seigo wrote: > > On Tuesday, February 1, 2011, Harri Porten wrote: > >> On Tue, 1 Feb 2011, Aaron J. Seigo wrote: > >> > we could end up with a "new kdelibs" module that contains just the > >> > core stuff such as kdecore, kdeui, kio ..

Re: proposal: remove KTextEditor interface from kdelibs repository

On Wednesday 09 February 2011, Stephen Kelly wrote: > Alexander Neundorf wrote: > > On Wednesday 09 February 2011, Stephen Kelly wrote: > >> Aaron J. Seigo wrote: > >> > On Tuesday, February 1, 2011, Harri Porten wrote: > >> >> On Tue, 1 Feb 2011, Aa

Re: splitting up kdebase in git

On Saturday 12 February 2011, Tom Albers wrote: > - Original Message - > > > On Saturday, February 12, 2011 19:12:41 Tom Albers wrote: > > > - Original Message - > > > > > > > Hi, > > > > > > > > Our default wallpapers used to be part of kdebase/workspace, but > > > > during > > > >

Re: A Qt replacement for KGlobal::ref and deref

On Monday 14 February 2011, Stephen Kelly wrote: > Aaron J. Seigo wrote: > > On Wednesday, February 9, 2011, Stephen Kelly wrote: > >> http://techbase.kde.org/Projects/KDELibsModifications > > > > good to see people thinking about these things. however: > > > > this page belongs on commuity.kde.org

Re: update on KDE Platform 11dev sprint -> announing possible dates and location!

On Thursday 06 January 2011, Kevin Ottens wrote: > On Wednesday 5 January 2011 19:15:18 Aaron J. Seigo wrote: > > we will have ~20 spots, though we may be flexible to accomodate a few > > more if needed. if you would like to attend, please add your name to the > > wiki page. if you have already don

Re: QZeitgeist and Phonon

On Tuesday 08 March 2011, John Layt wrote: > On Monday 07 March 2011 23:58:08 Trever Fischer wrote: > > Very recently, we introduced an optional build time dependency on > > QZeitgeist. Today, someone said I should mention this to k-c-d. So here > > goes: > > That was me, I was just concerned we we

Re: kdegraphics has (mostly) moved to git

On Monday 14 March 2011, Michael Jansen wrote: > Noone interested here? If noone speaks up i will just make the change > assuming noone cares. > > Mike > > On Sunday 06 March 2011 01:47:54 Michael Jansen wrote: > > On Friday 04 March 2011 20:49:08 Alex Merry wrote: > > > kdegraphics has now moved t

Re: Dependencies Policy?

On Friday 18 March 2011, John Layt wrote: > Hi, > > I was wondering if we need to define a "New Dependencies" policy, or at > least some guidelines to remind people what to think about when choosing or > creating new dependencies? Sounds reasonable. > Something like: > * All new dependencies must

Re: 4.6 branches created in git again

On Sunday 20 March 2011, Parker Coates wrote: > On Sun, Mar 20, 2011 at 10:09, Andreas Hartmetz wrote: > > On Sunday 20 March 2011 14:38:40 Albert Astals Cid wrote: > >> Can you please be careful and do not create incorrectly 4.6 branches in > >> places where the branch is called KDE/4.6 (e.g kdeli

Re: 4.6 branches created in git again

On Monday 21 March 2011, Ian Monroe wrote: > On Sun, Mar 20, 2011 at 09:17, Ian Monroe wrote: > > On Sun, Mar 20, 2011 at 09:09, Andreas Hartmetz wrote: > >> On Sunday 20 March 2011 14:38:40 Albert Astals Cid wrote: > >>> Can you please be careful and do not create incorrectly 4.6 branches in >

Re: Help in modularization

On Wednesday 06 April 2011, Kevin Ottens wrote: ... > [*] I wish we had a CI system in place... We have it basically ... almost. We have projects setup on my.cdash.org for all KDE modules, and everybody can contribute nightly builds there. The scripts are in svn quality/nightly-support/. I'd be m

git and commitfilter ?

Hi, is commitfilter (http://commitfilter.kde.org) actually working with git ? Just today I figured that there is such silence wrt. to commit emails for kdelibs/cmake/modules/ because probably commitfilter is not working with git ? Is there an equivalent for it ? Or should I do the filtering on

Re: Help in modularization

On Wednesday 13 April 2011, Joel Bodenmann wrote: > So you'd need some help? Tell me what and give me some introductions etc.. It took me some time to respond because I thought I haven't written down anything yet... but actually I have already: http://techbase.kde.org/Development/CMake/Dashboard

Re: Please, return removed Konqueror feature bug (embedded advanced text editor) in KDE 4.6

On Tuesday 19 April 2011, Josef Spillner wrote: > :: David Faure Dienstag 19 April 2011 > > > > I can see how some users are saying "yes", but a large majority of users > > has been criticizing konqueror for the amount of menus and toolbars, so > > adding editing functionality will just make it loo

Re: libtagaro -> kdereview [-> kdegames]

Hi, On Thursday 21 April 2011, Stefan Majewsky wrote: > Hi, > > what is the technical procedure for moving libtagaro.git to kdereview? > I think sysadmins need be informed, and hope that those are reading > here. Any chance it could get a name which makes you kind of understand what it is ? libkd

Re: Git Feature Branch Naming Policy

On Tuesday 26 April 2011, John Layt wrote: > Hi, > > Did anything come out from discussions on feature branch naming in git? > With GSoC starting soon we'll be getting a lot of new feature branches and > it would be nice if they were consistantly named to make them easy to find > and manage. > > S

Re: Empty merges per release

On Wednesday 27 April 2011, Thiago Macieira wrote: > I know we decided to use cherry-picks to bring commits from past versions > to master, Is this what is described here ? http://techbase.kde.org/Development/Tutorials/Git/Recipes Our git docs are still not in good shape: http://techbase.kde.o

Re: Empty merges per release

On Wednesday 27 April 2011, John Layt wrote: > On Wednesday 27 Apr 2011 17:52:32 Alexander Neundorf wrote: > > On Wednesday 27 April 2011, Thiago Macieira wrote: > > > I know we decided to use cherry-picks to bring commits from past > > > versions to master, > > &

  1   2   3   4   >