Qt 6.7 still only requires CMake >= 3.16, like Qt 6.5 and
6.6, so this does not really change anything for this discussion.
Kevin Kofler
n version number arithmetic).
Kevin Kofler
Heiko Becker wrote:
> On Monday, 23 September 2024 21:52:38 CEST, Kevin Kofler wrote:
>> Hi,
>>
>> I would like to request unarchiving the Trojitá project and assigning
>> maintainership to me.
>
> I like to get it back, too.
Are you willing to maintain it tog
cheats because it simply does not let me access mails older than 2
weeks at all, it includes them in the message counts, but they are
completely filtered out from view).
Kevin Kofler
the newer Mozilla DeepSpeech, etc.
The Free Software implementations that you can run locally all focus on
doing one thing well, not on offering a complete solution like the Google
Translate web service does. Integrating that all into a complete solution is
then your job as the application developer.
Kevin Kofler
e (!)? Do we not have enough pointless porting busywork for the
incompatible Qt major releases yet, so now we need the same for KDE Builder?
Kevin Kofler
a kontain a 'k', so
I think those are kooler. ;-) (Yes, the misspellings of "contain" and
"cooler" in the previous sentence were intentional. ;-) )
Kevin Kofler
aybe
even both (in favor of a completely new one). But if you are going to
revisit the Phonon API anyway, it may be worth considering to work with
QtMultimedia instead.
I would rather have one working multimedia framework for Qt than two
half-unmaintained ones.
Kevin Kofler
to depend on a library that requires C++20 to build? Either we can use C++20
or we cannot.
Kevin Kofler
t would mean at least one of the two APIs will go
away, maybe even both (in favor of a completely new one). But if you are
going to revisit the Phonon API anyway, it may be worth considering to work
with QtMultimedia instead.
I would rather have one working multimedia framework for Qt than two
half-unmaintained ones.
Kevin Kofler
Frameworks later.
Kevin Kofler
render and Okular cannot, so that is why I am asking how they
compare.
Kevin Kofler
render and Okular cannot, so that is why I am
asking how they compare.
Kevin Kofler
tatic
mailing list archives is not.
Broken links sound like a showstopper to me. […]
openSUSE developed a way to map legacy discussions on mlmmj to
HyperKitty, while Fedora just retained the old Pipemail static pages.
Either works.
So either solution would need to be implemented on KDE mailing lists too.
Kevin Kofler
Kevin Kofler wrote:
> What am I expected to use with my PinePhone? Does
> https://apps.kde.org/keysmith/ work?
To answer my own question: Yes, Keysmith works, both on the desktop (and
notebook) and on the PinePhone. It is also easily possible to synchronize
the keyring between different d
area characters like the Font
Awesome ones. And other operating systems might not even attempt to fall
back to a font that actually provides the icon. Windows at least used to
have no such fallback mechanism, though I have not used it for years, so
that might have changed since.
Kevin Kofler
eem to be currently deployed in
Fedora at least, they are using what I assume to be a static copy of the old
archives) is IMHO required.
Kevin Kofler
y some project, but it does not seem to be currently deployed
in
Fedora at least, they are using what I assume to be a static copy of the
old
archives) is IMHO required.
Kevin Kofler
Kevin Kofler wrote:
> What am I expected to use with my PinePhone? Does
> https://apps.kde.org/keysmith/ work?
To answer my own question: Yes, Keysmith works, both on the desktop
(and notebook) and on the PinePhone. It is also easily possible to
synchronize the keyring between different d
PR requires using state-of-the-art technology to protect
> personal information, using 2FA is, in my opinion (but I'm not a lawyer),
> a must for any website that stores personal information.
See above, almost nobody else does this, so that interpretation of the GDPR
is pure nonsense.
Kevin Kofler
Ben Cooksley wrote:
> On Mon, Oct 24, 2022 at 3:36 AM Kevin Kofler
> wrote:
>> IMHO, this is both an absolutely unacceptable barrier to entry and a
>> constant annoyance each time one has to log in.
>
> You shouldn't have any issues with remaining logged in as long a
PS:
Kevin Kofler wrote:
> Ben Cooksley wrote:
>> I have also enabled Mandatory 2FA, which Gitlab will ask you to configure
>> next time you access it.
>
> IMHO, this is both an absolutely unacceptable barrier to entry and a
> constant annoyance each time one has to log
n the same
device as the web browser (both on the smartphone or even both on the
desktop/notebook)? You just cannot. (As far as I know, even Yubikeys can be
emulated in software.) Two-factor is a farce.
Kevin Kofler
some dependency's copy of the
license, the license really has to be included with every tarball.)
Kevin Kofler
re dumps can be very huge, which means uploading them can actually take
longer than downloading the debugging information on asymmetric consumer
broadband, and which also means it can come out expensive on metered or
capped Internet connection plans.
Kevin Kofler
ly, Index is an extremely generic name.
Kevin Kofler
turn new MarkdownPart.
>
> Similar lines exist in markdownpart.cpp, though there you use auto almost
> in all these cases.
IMHO, this just makes the code harder to read (as most uses of "auto").
Kevin Kofler
rs.
So seeing this stated as the main reason for having switched to GitLab
strikes me as very odd.
Kevin Kofler
pecially because everyone
depends on this new monopoly now. (I see more and more big Free Software
projects moving to it.)
I think we really need either an uncrippled fork of GitLab or the
high-profile users switching to really Free, not crippled, forges.
(What was wrong with Phabricator?)
Kevin Kofler
get away with it
depends on what the files do and what license they fall under.)
I personally do not think that it is acceptable for an image viewer to
require an Internet connection at runtime. Your proposed solution only moves
the problem instead of solving it.
Kevin Kofler
lding machines even *have* an internet connection during configure /
> build stages).
Yep, this is an absolute no go in Fedora. The build system (Koji) has all
Internet connection deliberately blocked. Packages MUST NOT attempt to
access the Internet during builds. No exceptions.
Kevin Kofler
may have promised to you without consulting me first)
may have caused to you. It will never happen the same way again.
Kevin Kofler
ttempts to bring this standardized C99 feature
into the C++ standard (and even got C11 to make it optional for C too).
Kevin Kofler
work for this, because it is not monotonic. What
you really want to know is whether you have something >= 5.65.0.abcd123, and
having a 5.65.0.commithash version is not going to tell you that.
Kevin Kofler
Harald Sitter wrote:
> Its master branch is still kdelibs4, the frameworks branch hasn't seen
> any progress in 21 months. Hasn't had a release in years. Very
> unmaintained all in all.
And there is also a working, maintained successor (Falkon).
Kevin Kofler
his feature a preference
as in the KatePart.
Kevin Kofler
t the crash is in JITted code (e.g., JavaScript
compiled by the V8 JIT), in which case you cannot possibly get a useful
backtrace at all, no matter how much debugging information you enable.
Kevin Kofler
Philipp A. wrote:
> No, because you’re missing something here: There’s no KF5 bindings. So
> every project that’ll use Shaheed’s new cool KF5 bindings will be a new
> project.
There is PyKDE4 that people will want to port their legacy programs from.
Kevin Kofler
LLVM users such as
Mesa/Gallium3D/llvmpipe).
ROOT is a huge bloated framework that is not exactly reputed for its
simplicitly to package.
Kevin Kofler
eme.
Kevin Kofler
Matthias Klumpp wrote:
> And since the spec allows themes to define arbitrary layouts, there is
> technically nothing wrong with the Breeze theme.
IMHO, doing things differently just because you can, even if it breaks KDE's
own ECM macros, is not helpful.
Kevin Kofler
Breeze paths to match the other themes?
The Fedora package actually creates a whole hierarchy of empty directories
such as 16x16/apps under Breeze:
http://pkgs.fedoraproject.org/cgit/rpms/breeze-icon-theme.git/tree/breeze-icon-theme.spec#n82
I think it would really be helpful to make Breeze match the de-facto
standard directory hierarchy.
Kevin Kofler
Kevin Kofler wrote:
> The new xkbcommon requirement is also an issue for us in Fedora. The new
> xkbcommon 0.7.0 is only available in Rawhide and it is doubtful that it
> will ever be backported to Fedora 25 or 24. So, if we cannot get
> libxkbcommon updated, we will either be unabl
absolutely
necessary to make your software work on some distributions. (Sure, in this
particular case, xkbcommon can be updated, if distribution policies allow
it. But you are talking about dependency changes in general, which can have
bumped sonames or other incompatibilities.)
Kevin Kofler
CI sysadmins for
an exception, and if the process (of course you have to wait for their
answer, and ideally for them to update the CI) makes you miss the feature
freeze, ask the release team for an exception to the freeze.
Kevin Kofler
quot;supported releases", I meant supported by the distribution. E.g., for
RHEL/CentOS, that is currently RHEL/CentOS 5, 6 and 7. For Fedora, that is
currently Fedora 24 and 25.
Kevin Kofler
oduce bugs, but only ones which
were already in the previous release.) As I understand it, this is exactly
the situation we are in with KWin and xkbcommon now.
Kevin Kofler
uot;make work". It is that or not have the code
at all. And the existing old version was already "broken" in the same way.
Kevin Kofler
i is the biggest pain point when it comes to the quality of the
software itself, and that is unrelated to the dependency issues you mention.
Kevin Kofler
Martin Gräßlin wrote:
> Everybody except I. I would have to maintain that mess. And I don't have
> time to maintain multiple compile time paths.
I don't see how it would be any more work to maintain #if FEATURE as
compared to #if 0.
Kevin Kofler
work and everybody will be happy.
Kevin Kofler
EST RHEL release, currently RHEL 7 from 2014. Or you could ignore
RHEL entirely and only consider fast-moving distros such as Fedora.)
Kevin Kofler
Still, we see it as a last
resort only.)
Kevin Kofler
This has become much worse
lately, with dependencies on bleeding-edge versions of: xkbcommon, Wayland
libraries, etc. (And KWin is one of the worst offenders there, though
definitely not the only one.)
Kevin Kofler
dependencies updated in stable releases
(or in the worst case, even in Rawhide).
Kevin Kofler
r build.kde.org to
>> fetch it.
>
> Mesa 13 is news to me.
This is also an issue for us: Mesa 13 is only available in Fedora 25
(updates) and Rawhide, not in Fedora 24.
Kevin Kofler
n
> surrect it from there.
Even if you stop releasing the kdelibs, distros will keep releasing them for
much longer, some for a lot longer. (E.g., we still also ship kdelibs3 in
Fedora and I have no plans to let it go.)
Kevin Kofler
0111204git.fc24.x86_64
tomahawk-0:0.8.4-12.fc26.x86_64
tomahawk-libs-0:0.8.4-12.fc26.i686
tomahawk-libs-0:0.8.4-12.fc26.x86_64
vtk-qt-0:6.3.0-11.fc26.i686
vtk-qt-0:6.3.0-11.fc26.x86_64
Kevin Kofler
infrastructure (QupZilla, the
Calamares webview module, etc.).
Kevin Kofler
Albert Astals Cid wrote:
> From my "i know nothing about random numbers", i guess it's hard to write
> a unit test for a sequente of random numbers, you can get ten "3" in a row
> and it's still a valid random sequence.
https://xkcd.com/221/ ;-)
Kevin Kofler
David Edmundson wrote:
> Sorry, I meant we should change the config that calls init-repository, not
> init-repository itself.
>
> It's in ci-builder-tools, I've made a patch.
I think you mean "--module-subset", not "--module-subest". (What's a
"subest"? ;-) )
Kevin Kofler
ht to you by KNode (through Gmane).
Kevin Kofler
laurent Montel wrote:
> We will not create more release from kdepim4, no distro uses it even
> debian :)
Fedora will ship (it's currently under review) a kdepim4 package containing
KNode and KTimeTracker, which are not included in the new KF5 kdepim.
Kevin Kofler
ion based on a variety of criteria,
including glyph coverage (OK, Noto is great there; your previous default
Oxygen was not, though!), quality, looks, etc. And most importantly, the
distro-wide aliases ensure consistency across applications using different
toolkits. Desktops deciding they know better break this.
Kevin Kofler
el. And you guys
have the even harder task porting to *BSD. Don't give up, it can be done.
Kevin Kofler
g=1 host_clang=1 clang_use_chrome_plugins=0 \
make_clang_dir=/usr
flags that desktop-linux.pri sets when building for a linux-clang target?
> - Example from qt3d (so external to this discussion), using a broken
> OffsetOf in a bundled third party library.
Yes, bundled libraries suck and this kind of issues is another reason why.
Kevin Kofler
se_system_* flags (point 2.) that I hardcoded to "=1".
But issue 1. is the bigger issue.
That said, your example is actually a bad example because
Chromium/QtWebEngine does not actually bundle giflib. (It uses its own GIF
decoder, which is forked from WebKit's, which is forked from Mozilla's.)
Kevin Kofler
en it comes to compatibility between
versions. Still, who knows what will happen in future versions? But the
points above are stronger arguments.
Kevin Kofler
iler, which may be an
older or patched one.
This is entirely a compatibility issue between 2 build tools (Flex and the
compiler), I don't see how this should be our (KDE's) problem.
Kevin Kofler
uld not. Generated files have no business being in a
source control or in source tarballs. "BuildRequires: flex" is one line in a
distro specfile.
Kevin Kofler
s. (I think it was about using stdint.h or something like that.) So I am
not surprised that they are now using C99 comments (which ARE compliant to
the current C standard, and have been for 16 years (!)).
Kevin Kofler
e name would prevent that (for the usual problems with
> ABI changes).
Not if you ship your not-yet-in-KF5 library with a soversion (soname major
version) < 5. (I'd just pick 0.)
Kevin Kofler
rary actually becomes
a Framework.
> 3) Moving something from "not a KDE Framework" to "KDE Framework" gives
> a last chance for fixing up abi/api.
If you need to fix the ABI, you should just bump the soname major version.
I'd just use libKF5*.so.0 (instead of the normal .5) for libraries that are
not yet Frameworks.
Kevin Kofler
sense for different applications. So this
should be done with per-application scripts. I would also strongly argue for
keeping this manual for all applications whose maintainer(s) didn't
explicitly opt in to such an autoclosing policy.
Kevin Kofler
Luigi Toscano wrote:
> Feedback on Phabricator gathered outside the BoF from people who could not
> attend:
Were there no complaints about the fact that you can still not view anything
at all without logging in?
Kevin Kofler
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124163/#review82295
---
Ship it!
Ship It!
- Kevin Kofler
On Juni 24, 2015, 12:33
Christian Mollekopf wrote:
> 4. Would be pretty good IMO, but unfortunately leads to an unexpressive
> interface (because QVariant can't be parametrized with valid values).
You would just document in the API documentation what types the returned
QVariant can take.
Kevin Kofler
h.
> This situation will not likely change as that there are old bug reports
> regarding this situation and they were never resolved.
And this is exactly why we urge KDE to not require QtWebEngine for anything.
Kevin Kofler
overflowed into March.)
Kevin Kofler
requiring ExcludeArch or ExclusiveArch lists all over the
place.)
Kevin Kofler
their browser than Apple. In fact, Chromium and Chrome
already have the reputation of hiding spyware (mis)features in their code.
Kevin Kofler
> On Feb. 9, 2015, 10:01 nachm., Kevin Kofler wrote:
> > IMHO, QUrl::fromUserInput(str, QString() QUrl::AssumeLocalFile) would be
> > safer. Or do you really think "dolphin nonexistentfile" should look up
> > "nonexistentfile" over DNS?
>
> Tho
::AssumeLocalFile) would be safer.
Or do you really think "dolphin nonexistentfile" should look up
"nonexistentfile" over DNS?
- Kevin Kofler
On Feb. 9, 2015, 12:48 nachm., Arjun AK wrote:
>
> ---
> This is an automatical
ll for data
lookup to be doable on the server side at least as easily as from client-
side JavaScript.
Kevin Kofler
ot; library.
+1, this "Digikam SC" nonsense really needs to stop! All the stuff that's
now bundled in Digikam should be a dependency of Digikam as it used to be in
the past.
Kevin Kofler
distribution-produced patch directly.)
So, with my distribution packager hat on, I think a web upload feature
should be a requirement. (I also agree with other posters that it would be
more friendly to newcomers, too.)
Kevin Kofler
in the further development of kdesvn.
I'd say just commit/push the patches. If there's no maintainer, there's also
nobody to complain. :-) ("Wo kein Kläger, da auch kein Richter.")
Kevin Kofler
l to run,
which is very nasty. If you give it a 0.x soversion and remember to
increment x on each BIC change, we will know to rebuild affected packages.
The only thing worse than ABI changes is SILENT ABI changes.
Kevin Kofler
ibfoo.so.0 is also very commonly used for the first stable-ABI version of a
library) and tracking binary incompatible changes in a sane way (without
losing the zero major version).
Kevin Kofler
st using Marble directly? Marble can already display
OpenStreetMap, and why do we want to support the non-Free Google Maps? (Does
embedding it into an application that way even conform to Google's terms of
service?)
Kevin Kofler
ranchname starts with username/", for example
> "sebas/hacking".
Why can't we just allow delete and force-push of all branches for all KDE
contributors? Hasn't it always been KDE policy that contributors are trusted
not to do stupid things? Why do we need to enforce this through technical
restrictions?
Kevin Kofler
t "we
either all switch and have uniformity or we don't and then we end up with
reviewborad+gerrit" (Albert Astals Cid), which to me sounds a lot like
blackmail (of course not by Albert, he's just the messenger).
Kevin Kofler
s as a failure
(it was always made clear that it is only an experiment and can be ended at
any moment), and kick out Trojitá from KDE if Jan absolutely wants to use
Gerrit. (It's not even a KF5 or kdelibs application, but a Qt-only one.)
Then he can use whatever tools he wants. Problem sol
Marco Martin wrote:
> In the past weeks I have been working on a new framework, called KPackage.
You ARE aware that KPackage was the name of an old frontend for RPM and
other package managers that used to be part of the KDE Software Compilation
4?
Kevin Kofler
ng to is
case-sensitive to begin with, and only install the compatibility headers on
case-sensitive file systems.
Kevin Kofler
laurent Montel wrote:
> Indeed it's not finish to port (I worked on it too).
> Still depend against kdelibs4support .
So what? That will only become a problem when Qt 6 gets released years from
now.
Kevin Kofler
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120697/#review68836
---
Ship it!
Ship It!
- Kevin Kofler
On Okt. 21, 2014, 7:15
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120676/#review68809
---
Ship it!
Ship It!
- Kevin Kofler
On Okt. 21, 2014, 2:53
are under /usr/include/kde4. :-)
Kevin Kofler
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120627/#review68677
---
Ship it!
Looks good now.
- Kevin Kofler
On Okt. 18, 2014
1 - 100 of 190 matches
Mail list logo
