a matching counterpart in the
Linux version, so I hope I didn't write the Windows code. ;)
- Michael Pyne
On Oct. 28, 2013, 10:07 a.m., Sune Vuorela wrote:
---
This is an automatically generated e-mail. To reply, visit:
http
% solution. Either way, even if kdesrc-build doesn't work, Michael
Jansen's excellent build-tool is out there as well.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde
downloading ECM would
actually be a workable option.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo
. But this central repository should be an actual listed
dependency instead of an auto-magical figment of CMake's imagination.
At the very least said magic should not be the only way to build with this
proposed central repo.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message
doesn't strike me as a strong problem in 2014. But on the other hand it might
still be an issue for embedded platforms, which I'm sure we'd want to support.
I don't know the defines for it though, sorry.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part
for the benefit of our current devs, infrastructure, and
interested third-parties/distribution packagers.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel
On Sun, November 10, 2013 20:11:07 David Faure wrote:
On Sunday 10 November 2013 13:44:09 Michael Pyne wrote:
I would highly recommend doing something similar to what was done for
strigi when it was split into 5 git modules.
I think you misunderstood the issue?
A super-repo might help
process for you entirely
(e.g. kdesrc-build or the KDE Superbuild repo which uses CMake) or
make it easier to script this yourself (kde-checkout-list.pl in
kde-dev-scripts, which might even be able to do the clones for you IIRC).
Regards,
- Michael Pyne
our header magic to keep KSDC and KImageCache separate.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
.
I'll try to resolve this tonight so that splitting may proceed.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman
with a fraction byte ;)
I think you're right. I forget why this was a double (I worked on this code
but I believe the API pre-dated my involvement).
How would this go about being changed? Are we still doing BIC Mondays ;) or
should I just do a review request?
Regards,
- Michael Pyne
signature.asc
), this setting
is configurable in the Other tab of the 'language' KCM (the Locale button
in KDE 4's System Settings).
I'm not sure where that was put in KF5/PW2 yet.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part
to use.
It's visible in the kde-build-metadata repo, and should make it easy enough to
manage (this is used in the same kf5-qt5-build-include that dfaure and others
are maintaining for the kdesrc-build KF5 config).
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed
should be able to use something like
options kwalletmanager
# your-options-here
end options
somewhere in your kdesrc-buildrc (as of kdesrc-build git from last month), and
kdesrc-build will use those options once the module shows up.
Regards,
- Michael Pyne
-metadata repository
has the right branch names for the modules (stored in the
logical-module-structure file) but I might audit that myself later as well. In
short if build.kde.org is happy with the KF5 modules kde-build-metadata is
probably correct.
- Michael Pyne
On Feb. 11, 2014, 7:23 a.m
might do this myself in the next day or so if there's no opposition, as
now is the easiest this transition is ever going to be, at least until KDE 4
development has well and truly stopped.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
about the renames. ;)
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
to see extra-cmake-modules
didn't already have a branch-group entry so I've fixed that in
kde-build-metadata.
- Michael Pyne
On Feb. 14, 2014, 2:10 p.m., Alex Merry wrote:
---
This is an automatically generated e-mail. To reply, visit
in frameworks!).
Hopefully someone else has an idea.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Sat, February 15, 2014 20:35:28 David Faure wrote:
On Thursday 13 February 2014 17:41:26 Michael Pyne wrote:
In the meantime I will fix kdesrc-build to fallback automatically to
git-clone like it's supposed to.
There's two cases:
- snapshot exists, but is broken. This is the current
programmatic consumption need to be async; I've been able to encounter
the most amazing deadlocks sometimes.
Of course this is both hard to do and hard to train/teach others to know how
to do. :-/
Regards,
- Michael Pyne
___
Kde-frameworks-devel
for me?
Yes, it should take care of it for you.
And as of now, it does.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
namespace
if it's at all possible (and it's almost always possible). This kind of thing
happens to us every so often and it's always avoidable by naming things
correctly.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks
.
According to the Qt commit log by Kai, the workaround appears to be people
should always have been using filter rules for this anyways.
I resorted to simply ifdeffing the offending lines of code out here locally
and things work great (if by work I mean compile ;)
Regards,
- Michael Pyne
become a big fan of --resume-from (or -after), --stop-before (or
-after) and --ignore-modules options myself. And always --pretend.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman
) then static_cast is
at worst unspecified, as opposed to undefined behavior where optimizers
start adding buffer overflows. So it still seems like the better answer here
unless we want to bring in some of those fancy image-swizzling graphics
libraries.
Regards,
- Michael Pyne
On Thu, February 27, 2014 11:35:16 Kevin Funk wrote:
Am Mittwoch, 26. Februar 2014, 23:27:08 schrieb Michael Pyne:
On Wed, February 26, 2014 22:30:48 Milian Wolff wrote:
Also, while at it, could we get a truly verbose flag, which actually
outputs the output from whatever tool is currently
, all the solutions are probably
equally a hack...
- Michael Pyne
On March 2, 2014, 8:20 p.m., Milian Wolff wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116542
On Tue, March 4, 2014 22:54:42 David Faure wrote:
On Tuesday 04 March 2014 01:32:14 Michael Pyne wrote:
kf5: Port rc files to use branch-groups consistently.
Thanks!
This should be absolutely transparent except that kde-kactivities will
rename to kactivities, though you might have
to KSharedDataCache
without having to define KSharedDataCache. It might even be possible to
forward-declare KSharedDataCache and use a typedef instead but I didn't even
do the porting work here and that didn't occur to me when I was reviewing the
patch a few months back.
Regards,
- Michael Pyne
to be looking for Qt4 specifically. You might want to see if kdesrc-
build didn't accidentally switch the source git-branch to the KDE4 one instead
of KDE5 one (it should list the branch it's using as it updates the module).
Regards,
- Michael Pyne
applications, but for sure I've
missed something (plasma for sure), in case of failures (and you depends on
a snapshot of KF5 and not the last alpha2) please fix it.
Thanks. I've also updated our Porting Notes at
http://community.kde.org/Frameworks/Porting_Notes
Regards,
- Michael Pyne
at
the return type of QListT::size().
src/lib/util/kuser_unix.cpp
https://git.reviewboard.kde.org/r/116798/#comment37271
Again, might want to put a setgrent() here.
src/lib/util/kuser_unix.cpp
https://git.reviewboard.kde.org/r/116798/#comment37272
And a setgrent() here.
- Michael
, and all tests pass.
- Michael Pyne
On March 15, 2014, 4:02 p.m., Alexander Richardson wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116798
they cleanly fit the problem.
src/lib/util/kuser_unix.cpp
https://git.reviewboard.kde.org/r/116883/#comment37546
A better name for callback would be something like handleNextGroupUser
or some other descriptive way of describing what the callback is actually
intended to do.
- Michael Pyne
On March
?
- Michael Pyne
On March 18, 2014, 8:14 p.m., Alexander Richardson wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116881
somewhere (e.g.
community.kde.org) or is this unwritten convention at this point?
Also, is there any reason that an application self-contained within a git
repository couldn't simply use doc/*.docbook or would that add difficulty
compared to doc/appfoo/*.docbook?
Regards,
- Michael Pyne
On Fri, March 28, 2014 10:16:29 Burkhard Lück wrote:
Am Mittwoch, 26. März 2014, 21:04:01 schrieb Michael Pyne:
On Wed, March 26, 2014 23:22:22 Burkhard Lück wrote:
Hi,
I think we need a similar *consistent* scheme for docbook location in
frameworks repos.
Agreed.
You've
it!
For the curious like me, see git show
8ec9cef7c68d2d995ceb85aa51839762b4406025 in kdelibs for the full story
behind this. But if nobody ever used it, it proves that it can be removed
indeed.
Yes indeed. :)
Regards,
- Michael Pyne
___
Kde
the
extra repo happens to be, if we're trying to combine these all into 2-3 repos.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On April 7, 2014, 3:24 p.m., Kevin Ottens wrote:
Any news?
Alexander Richardson wrote:
Still wondering whether I should always use getgrouplist since AFAIK no
platform without it is supported (yet) or should keep the fallback code.
Flip a coin if you have too. :)
As long as the
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116881/#review55243
---
Ship it!
Ship It!
- Michael Pyne
On April 8, 2014, 8:30
as additional
parameters (you might want to add -p as well to print out the module name as
part of the output).
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks
build.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
to double-check as well if you haven't already.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
out if a review request
applies to a framework module you're maintaining or not. ;)
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
.
Thanks,
Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
there are definite SIC
concerns. In fact that's one comment that could be made; we'd still need up
update our porting guide if this change goes in.
- Michael Pyne
On May 1, 2014, 1:03 a.m., Michael Pyne wrote:
---
This is an automatically
generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/117919/#review57786
---
On May 1, 2014, 1:03 a.m., Michael Pyne wrote:
---
This is an automatically generated e-mail
On May 12, 2014, 3:18 p.m., Kevin Ottens wrote:
Indeed looks like something which got forgotten along the way. K4About* is
supposed to be the porting tool, so let's have this one in even if that's
SIC.
Michael Pyne wrote:
To be clear, should I remove the deprecated ctor too
downstream code needs
porting after this to fix the naming of the license in its KAboutData ctor.
Thanks,
Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
of a git repo anymore, as long as it's setup
right in logical-module-structure.
When you get dependencies right, don't forget to commit! ;)
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org
for someone with actual
KDirWatch experience give the +1.
- Michael Pyne
On June 1, 2014, 9:03 p.m., Matthew Dawson wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/118458
-commit template reminding to use an appropriate
REVIEW keyword so that devs don't have to wait until they try to push to
figure out their commit can't land as-is.
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel
On Sat, June 21, 2014 19:34:21 Kevin Ottens wrote:
On Saturday 21 June 2014 11:22:28 Michael Pyne wrote:
On Thu, June 19, 2014 23:21:22 Marco Martin wrote:
Hi all,
I was thinking, since the policy for committing in frameworks is to
always
asking for a review, what about
/r/119275/
---
(Updated July 15, 2014, 9:36 p.m.)
Review request for KDE Frameworks, Alex Merry and Michael Pyne.
Repository: kcoreaddons
Description
---
Using the same variable name for var1 and var2 in the new
for me.
- Michael Pyne
On July 18, 2014, 1:31 p.m., Alexander Richardson wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/119356
of the hottest
methods in KIconLoader that much slower).
However I thought the KCM for the Desktop Theme Appearance already reset the
cache as suggested by Aleix. Is this for situations where the theme is somehow
changed via other means (such as direct edits to the rc files)?
- Michael Pyne
?
Regards,
- Michael Pyne
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
be best just for kapidox to download the file
directly via anonymous SVN (at least as a first priority).
Alternately, maybe we can setup a more server-friendly API for this (RESTful,
SOAP, link to a static file that is updated when the SVN is, etc.)?
Regards,
- Michael Pyne
On Sat, August 16, 2014 17:33:48 Michael Pyne wrote:
To be more clear, it might be best just for kapidox to download the file
directly via anonymous SVN (at least as a first priority).
Never mind, there's already an open review request for exactly this, sorry for
the noise.
Regards
option though: It is
used to pick the right branch or track if not specified, or it is used as CI
would use it, to pull in an entire set of divisions in one fell swoop. I'm
open to other ideas, but that's a topic for a separate thread in any event.
Regards,
- Michael Pyne
frameworks depend on themselves.
Is that intended, just an artifact or a bug?
Artifact, it's listing modules in a proper build order (not simply a list of
deps), but you're right: it should not list the last module since this is
supposed to be a dependency listing.
Regards,
- Michael Pyne
On Mon, August 25, 2014 22:18:13 Michael Pyne wrote:
On Mon, August 25, 2014 22:26:50 Marko Käning wrote:
Hi,
I just see (on the OSX/CI system) using e.g.
---
$ cd ~/scripts/dependencies/tools
$ list_dependencies frameworks/kauth
desupport/extra-cmake-modules
Qt5[stable
On Sept. 12, 2014, 10:49 a.m., Christoph Feck wrote:
Use KPixmapSequence if you need to access an FDO animation icon.
Dan Vrátil wrote:
That's the thing: I want to feed the animation icon to KPixmapSequence,
but KPixmapSequence only accepts full file path, or QPixmap. And I can't
for posterity's
sake (there shouldn't even be a binary change). trunk was already fixed.
Thanks for the report, and keep that keen eye open!
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
On Friday, January 14, 2011 19:38:19 Michael Pyne wrote:
On Friday, January 14, 2011 13:58:34 Dawit A wrote:
Can the warning message below be commented out if it is not critical ?
It simply overwhelms my ~/.xsession-errors file to the point where I
cannot look for other error messages
is missing from waitpid(2), or
the more recent waitid(2)? Both of those allow you to wait for specific
processes. It would have to be done in an alternate thread to avoid blocking
but you've already mentioned using a separate thread to support the current
SIGCHLD signal handler.
Regards,
- Michael Pyne
on kdesrc-build git. If you want to give it
a shot I'd appreciate it, if not that's fine too. Do keep in mind that I will
be once again extraordinarily busy over the working week so if I horribly
broke something I may not be able to fix it til the weekend.
Happy building!
Regards,
- Michael Pyne
.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
On Monday, January 31, 2011 17:48:38 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
and it shows the command line for
about 95% of the commands it would run. In short it is (my idea of) a bum-
standard build system, or as close as I can get it in an automated script.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
be an
improvement...
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
, or be reimplemented in a
different fashion (such as gcc intrinsics, I would imagine).
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
around, so we need another
solution i think.
I thought we were keeping SVN around for translations? Or will they simply
migrate after the rest of the modules have?
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
devil's advocate, is it not possible in theory to make
QAtomicPointer derive from QBasicAtomicPointer2 in Qt 4.8, in a way such that
users of *only* QAtomicPointer still worked but users of QBasicAtomicPointer
broke?
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed
On Tuesday, February 15, 2011 00:51:38 Thiago Macieira wrote:
On Monday, 14 de February de 2011 18:22:20 Michael Pyne wrote:
Well to play devil's advocate, is it not possible in theory to make
QAtomicPointer derive from QBasicAtomicPointer2 in Qt 4.8, in a way such
that users of *only
.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
some other technical solution to allow for a
rebase-based workflow, such as your idea regarding lumping everything into a
simple notification email (although this means CIA.vc and possibly things like
Commit Filter wouldn't work... :( )
Regards,
- Michael Pyne
signature.asc
Description
the changes verify that this was
an intended side effect of the change. ;)
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
to residents of Europe.
I think it's fairly obvious that John's using the first form and probably
never even heard of that second interpretation, so I wouldn't worry too much
about it. ;)
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
,
KSharedDataCache is KDE's only current caching system.
Michael Pyne, if you're reading this, please try hard to upstream
KSharedDataCache. It's a really nice, fast and stable solution.
I wouldn't mind pushing it to the Qt level, but I do think it would not
necessarily be as generic as necessary to be part
be
a net loss for the git.kde.org server.
Just let me know what is desired either way and kdesrc-build will support.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
be a solution?
Sounds like the best solution IMHO.
if so i can get it this weekend.
Thanks!
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
sure that this get double-checked before the release candidate stage?
Perhaps it could be done as part of branching the release branch (although
that would imply that was done by following some kind of procedure or
checklist as well).
Regards,
- Michael Pyne
signature.asc
Description
almost broke KSharedDataCache in a way I wouldn't have been able to easily
test until I took a bit more time to think about what the code was actually
doing now, and needed to be doing.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
/kdesupport_trunk
prefix /d/kde/inst/kde_frameworks
kdesrc-build users do not necessarily need this line. ;)
If you do use prefix just make sure the path is whereever you want kdelibs
(frameworks branch) to be installed.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message
, there's still someone mostly-active who
can show interested parties around the codebase and I should have piped in on
one of these requests awhile ago (but I've always assumed someone else has
need the help more ;( )
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed
next week so I
hope this doesn't add fuel to some fire somewhere, but hopefully this helps. I
can gzip the logs I have an upload them somewhere if that's helpful.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
On Saturday, August 27, 2011 21:27:06 Michael Pyne wrote:
On Monday, August 22, 2011 11:33:49 Jeremy Whiting wrote:
Was this decided upon at some point? I got conflicting stories from
sysadmin and other developers. Yesterday after migrating kdeaccessibility
to git I was asked
files provide a superset of mime-type info. There's probably a good
underlying question here (such as why use .desktop files for mime types now
that we have shared-mime-info) but the reason Name fields in .desktop files
are translated is an easy enough answer.
Regards,
- Michael Pyne
.
module qt-copy
repository git://anongit.kde.org/qt
# or kde:qt if you've got the prefix setup...
configure-flags ...
end module
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
) is that at some point *we* have to be responsible for the
parts of code the makeup KDE software. Obviously we can't do it all (and
that's not the point) but we just need to make sure stuff we're kicking
upstream is stuff that we won't need to fix/alter quickly if needed.
Regards,
- Michael Pyne
, an even worse case would
be a semantically different automated port.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
On Tuesday, September 13, 2011 14:25:02 Alexander Neundorf wrote:
On Wednesday, September 07, 2011 02:11:11 AM Michael Pyne wrote:
I really think the underlying concern is less about that per se but is
instead two-pronged:
...
2) Porting KClasses to functionally equivalent QClasses
should still be binary compatible if you
replace kdelibs 4.7.1 with kactivities+kdelibs 4.7.2, no?
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
module kdelibs
branch KDE/4.7
end module
kdesrc-build will then feed that option into its internal definition with
kdelibs while leaving the build order unchanged.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
, but the only times I've touched Activities has been completely by
accident, since I use the laptop for basically one thing. So while Activities
should guide power management I'd really hate for them to become the /only
way/ to control power management.
Regards,
- Michael Pyne
signature.asc
the power management options in that new one, and switch to
that new activity to do *the same thing* they were doing before. The only one
doing something different now is the *computer*. This is my point about
orthogonality.
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally
what's there than to debate about what's going to be there. ;)
Regards,
- Michael Pyne
signature.asc
Description: This is a digitally signed message part.
1 - 100 of 533 matches
Mail list logo
