Re: kaudiocreator to unmaintained
El dimarts, 21 de maig de 2019, a les 18:50:36 CEST, Nate Graham va escriure: > > On 5/21/19 10:48 AM, Kevin Ottens wrote: > > I'd like it to be part of KDE Applications. Unlike Zanshin I'd rather have > > this one tied to the Applications release cycle. That being said, it's been > > eons since I had anything in the regular applications collection. Could > > someone refresh me on what it entails to "make release"? Back in the day it > > was fairly transparent, if that's still so low on work I can easily say > > yes... > > if not I'll have to evaluate. > > If it's a part of KDE Applications, the apps release team will take care > of that for you. :) > > Sounds good, let's get kaudiocreator added to the bundle. I don't want to block on this, but given it seems relatively likely the "community" would be doing maintaince on this if it joins KDE Applications, I'd really welcome if this wouldn't depend on kdelibs4support. Has anyone attempted to port away from it? Cheers, Albert > > Nate > >
Re: kaudiocreator to unmaintained
On 5/21/19 10:48 AM, Kevin Ottens wrote: I'd like it to be part of KDE Applications. Unlike Zanshin I'd rather have this one tied to the Applications release cycle. That being said, it's been eons since I had anything in the regular applications collection. Could someone refresh me on what it entails to "make release"? Back in the day it was fairly transparent, if that's still so low on work I can easily say yes... if not I'll have to evaluate. If it's a part of KDE Applications, the apps release team will take care of that for you. :) Sounds good, let's get kaudiocreator added to the bundle. Nate
Re: kaudiocreator to unmaintained
Hello, On Monday, 20 May 2019 01:10:27 CEST Jonathan Riddell wrote: > Do you plan to push this commit. Just done now. > Will you make releases? I'd like it to be part of KDE Applications. Unlike Zanshin I'd rather have this one tied to the Applications release cycle. That being said, it's been eons since I had anything in the regular applications collection. Could someone refresh me on what it entails to "make release"? Back in the day it was fairly transparent, if that's still so low on work I can easily say yes... if not I'll have to evaluate. Regards. -- Kevin Ottens, http://ervin.ipsquad.net signature.asc Description: This is a digitally signed message part.
Re: Review Request: plasma-thunderbolt
On Wed, May 15, 2019 at 03:27:07PM +0200, Daniel Vrátil wrote:
> plasma-thunderbolt is a new repo containing, you guessed it, Thunderbolt KCM
> for Plasma. I initially submitted the code as a patch against plasma-desktop
> [0], where it got reviewed, but it was ultimately decided to better put it
> into a separate repository, since it's not just a KCM but also a library and
> a
> KDED module. I have backported all the changes from the Phabricator review
> back to the repository, so the code in the repo is identical to the one in
> the
> Phab review (minus buildsystem changes and a small build fix for clang).
>
> However, since this is still a new code, it must formally pass through
> kdereview before I can submit it into Plasma as a new module.
>
> Thus I'd kindly ask you to take one more look at the codebase [1] and let me
> know if there are any more issues to fix, or if we can proceed to include
> this
> in the next Plasma release.
Installing the bolt package on Debian/Ubuntu/KDE neon I have this file
/usr/lib/x86_64-linux-gnu/boltd
But it is not found by FindBolt.cmake
I need to add this to the search path ${LIB_INSTALL_DIR}
Looks great but I don't have anything Thunderbolt so it's just a white box :)
Jonathan
Re: Symmy in kde-review
On 27/04/19 18:46, Ingo Klöcker wrote: > On Montag, 22. April 2019 17:57:42 CEST Elvis Angelaccio wrote: >> On 12/04/19 13:12, Adriaan de Groot wrote: >>> # Runtime >>> >>> Since it's supposed to be a CLI application, you might want to massage the >>> QPA loading a bit, since when I run it (ssh'ed in to my build machine) It >>> does >>> this: >> Note that even if it can be used from CLI, it's still a GUI app as it >> needs Qt Widgets to show the passphrase dialogs. > > Hmm. I'm wondering why you don't leave the passphrase handling to gpg (resp. > gpg-agent) which will show a passphrase dialog (via one of the pinentry > implementations) if necessary. One of the major design goals of the gpg2 > architecture was that passphrase and secret key handling is done by gpg-agent > exclusively. Hi Ingo, the passphrase handling is still done by gpg-agent. gpgme allows to use a custom dialog instead of pinentry, which is what I've done to achieve better integration with Plasma. Cheers, Elvis > > Regards, > Ingo >
Re: Kdiff3 renovation
Will do this Friday at the latest? On Mon, May 20, 2019, 11:46 AM Jonathan Riddell wrote: > Seems like there's two releases been made, congrats. > https://download.kde.org/stable/kdiff3/ > There's been no announcement that I've seen, can you send one to the > kde-apps-announce@ list? > https://marc.info/?l=kde-announce-apps=1=201905=2 > > Jonathan > > > On Thu, 9 May 2019 at 16:19, Michael Reeves wrote: > >> >> Just a heads up kdiff3 is about to go through some major renovation. >> Currently file processing is extremely in efficient. There are at least >> three loops through the entirety of the data. Further more thee complete >> copies are kept in memory. Changing this will require almost a complete >> rewrite of the loading routines. These changes carry potential for breakage >> in kdiff3's compassion routines. I will try to avoid this but this area of >> kdiff3 is both complex and fragile. This is master only do to the extent of >> changes required. >> >
