https://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552018-12-16T01:53:43ZParabola Issue TrackerPackages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108792018-12-16T01:53:43Zfreemor
<ul></ul><p>Or perhaps we should just pull all of KDE as it is mostly based on QT and there is a lot of this, "Thing that has no business needing web browser functionality suddenly requires most of Chrome (qt-webengine)" .</p>
<p>I understand I'd be a serious blow to those using KDE but the fact is it's facing a creeping death already as one bit after another fall to this.</p>
<p>I can understand @dllud's and/or KDE users frustration. It's gotta be hugely annoying to watch as pieces keep falling off you DE.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108812018-12-16T02:23:41Zdllud
<ul></ul><p>CMakeLists.txt:131 from marble-18.12.0.tar.xz [1] shows that this package should build nicely without webengine. <br /><pre><code class="text syntaxhl"> find_package(Qt5 ${REQUIRED_QT_VERSION}
COMPONENTS
WebEngine
WebEngineWidgets
)
if ( NOT Qt5WebEngineWidgets_FOUND )
set ( MARBLE_NO_WEBKITWIDGETS TRUE )
endif()
</code></pre></p>
<p>I will give it a go and report back.</p>
<p>[1] <a class="external" href="https://download.kde.org/stable/applications/18.12.0//src/marble-18.12.0.tar.xz">https://download.kde.org/stable/applications/18.12.0//src/marble-18.12.0.tar.xz</a></p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108832018-12-16T04:42:47Zdllud
<ul></ul><p>Built successfully without qt5-webengine. I am now running marble-qt with no issues so far. Thus no need to remove these packages, but you will have to rebuild them.</p>
<p>On the PKGBUILD, besides removing qt5-webengine, I also had to take out some <code>rm</code> commands because I was getting <code>cannot remove XXX</code> errors. Not sure if it was the right thing to do. I am pasting the full diff bellow.</p>
<p>This should be easy to put into ABSLibre. Can someone do it? Otherwise, if you would like me to put it into ABSLibre or a personal repo, please instruct on how should I get the necessary push permissions.</p>
<pre><code class="text syntaxhl">diff --git a/marble/trunk/PKGBUILD b/marble/trunk/PKGBUILD
index 4e6ddff..b5f0237 100644
--- a/marble/trunk/PKGBUILD
+++ b/marble/trunk/PKGBUILD
@@ -13,7 +13,7 @@ arch=(x86_64)
url="https://www.kde.org/applications/system/marble"
license=(GPL)
makedepends=(extra-cmake-modules gpsd kdoctools knewstuff kparts krunner libwlocate phonon-qt5
- plasma-workspace qt5-serialport qt5-tools qt5-webengine shapelib)
+ plasma-workspace qt5-serialport qt5-tools shapelib)
source=("https://download.kde.org/stable/applications/$pkgver/src/$pkgbase-$pkgver.tar.xz"{,.>
sha256sums=('db39df148d327a61fd6080d4b3e55c8734762e4042c98386229fe3fbbcd85f52'
'SKIP')
@@ -40,7 +40,7 @@ build() {
package_marble-common() {
pkgdesc='Common libraries and plugins for Marble'
- depends=(qt5-svg qt5-webengine phonon-qt5 desktop-file-utils)
+ depends=(qt5-svg phonon-qt5 desktop-file-utils)
optdepends=('gpsd: GPS based geolocation'
'libwlocate: WLAN based geolocation'
'qt5-serialport: APRS plugin'
@@ -50,13 +50,11 @@ package_marble-common() {
cd build
make DESTDIR="$pkgdir" install
- rm -r "$pkgdir"/usr/share/{config.kcfg,kxmlgui5,metainfo,plasma} \
+ rm -r "$pkgdir"/usr/share/{metainfo,plasma} \
"$pkgdir"/usr/bin \
- "$pkgdir"/etc \
"$pkgdir"/usr/lib/qt/{qml,plugins/*.so} \
- "$pkgdir"/usr/share/applications/{marble_geo.desktop,marble_worldwind.desktop,org.kde>
- "$pkgdir"/usr/share/kservices5/{marble_part.desktop,plasma*} \
- "$pkgdir"/usr/share/locale/*/LC_MESSAGES/*.mo
+ "$pkgdir"/usr/share/applications/org.kde.marble*.desktop \
+ "$pkgdir"/usr/share/kservices5/plasma*
}
package_marble-qt() {
@@ -77,5 +75,4 @@ package_marble() {
make -C src/plasma DESTDIR="$pkgdir" install
make -C src/plasmarunner DESTDIR="$pkgdir" install
make -C src/thumbnailer DESTDIR="$pkgdir" install
- rm -r "$pkgdir"/usr/share/{icons,doc/HTML}
}
</code></pre> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108852018-12-16T05:48:35Zbill-auger
<ul><li><strong>Priority</strong> changed from <i>bug</i> to <i>freedom issue</i></li><li><strong>Subject</strong> changed from <i>marble depends on qt5-webengine</i> to <i>[marble[: depends on qt5-webengine</i></li></ul><p>good job, dllud</p>
<p>the 'qt5-webengine' dependency is actually associated with 'marble-common'; which is required by 'marble'</p>
<p>the bigger issue with this, is that 'marble' is in both the 'kde-applications' and 'kdeedu' package groups, and a hard dependency of 'kdeedu-meta'; so there could be a cascading effect of its removal</p>
<p>freemor wrote:</p>
<blockquote>
<p>Or perhaps we should just pull all of KDE as it is mostly based on QT and there is a lot of this, "Thing that has no business needing web browser functionality suddenly requires most of Chrome (qt-webengine)" .</p>
</blockquote>
<p>that has been discussed in the past - it was decided that we would keep supporting KDE until it became impossible, which very well could happen at the proliferation rate of this insane "every application needs an embedded web browser" trend</p>
<p>a few months ago, lucid-eagle tried to make a parabola/KDE liveISO - he had some real issues with it but with some manual intervention it was still possible to run most of KDE on parabola</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108872018-12-16T05:48:47Zbill-auger
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-9 priority-1 priority-lowest parent" href="/issues/1167">Freedom Issue #1167</a>: [chromium][electron][qt5-webengine][qt6-webengine] QTWebgine/Electron embeds "entire Chromium platform"</i> added</li></ul> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108912018-12-16T06:01:57Zdllud
<ul></ul><blockquote>
<p>there could be a cascading effect of its removal</p>
</blockquote>
<p>There's no need to remove this one in particular. Removing qt5-webengine from the PKGBUILD as I mentioned above works and delivers all 3 packages (marble, marble-qt and marble-common) in a usable state.</p>
<p>Please tell me whether some dev can add this to ABSLibre, or if and how I can do it myself.</p>
<p>It is worthwhile to check if other KDE applications also have soft dependencies on qt5-webengine like Marble.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108952018-12-16T06:17:28Zbill-auger
<ul><li><strong>Subject</strong> changed from <i>[marble[: depends on qt5-webengine</i> to <i>[marble]: depends on qt5-webengine</i></li></ul><p>yes you did good - someone will get to this at the next convenience</p>
<p>keep in mind that this is a relatively low-priority concern - the core 'base' system is non-graphical; so there are no essential packages that could possibly use 'qt5-webengine'; and anyone who has such a package installed, can most likely continue to use it indefinitely - they just wont get any upgrades - for that same reason, there is little value in identifying every package that depends on 'qt5-webengine', because they would necessarily be impossible to actually install - the only noticeable effect of removing them, is that pacman would not index them</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108962018-12-16T06:29:59Zdllud
<ul></ul><p>(Thanks for the prompt reply.)</p>
<blockquote>
<p>this is a very low-priority concern</p>
</blockquote>
<p>I understand. I had an issue with it though:</p>
<p><code>pacman -Syu</code> upgraded <code>marble-qt</code> but failed to upgrade <code>marble-common</code> due to the missing dependency. I was left with mismatching versions of these two packages on my system. (There seems to be no constraint to keep both packages at the same version.) I could still run Marble with no apparent issue, but I guess that won't always be the case if these two package keep drifting apart.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=108972018-12-16T06:35:16Zbill-auger
<ul></ul><p>yes that is an unfortunate policy of QT to modularlize everything the way they do - it is a good idea in theory; but in practice, most of the modules end up be tightly coupled to the same version of the others, negating much of the benefits of modularization - the primary effect of which being no more than long dependency lists for most QT packages</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=113232019-02-12T10:42:18Zoaken-source
<ul><li><strong>Assignee</strong> set to <i>oaken-source</i></li><li><strong>Status</strong> changed from <i>open</i> to <i>in progress</i></li></ul><p>I'm currently building marble-common without the qt5-webengine dependency.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=113242019-02-12T12:35:03Zoaken-source
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>in progress</i> to <i>fixed</i></li></ul><p>marble-common without a qt5-webengine dependency is in [libre] now.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=113252019-02-12T15:39:16Zdllud
<ul></ul><p>Thanks! Shouldn't it be removed/filtered from [extra]?</p>
<pre><code class="text syntaxhl">pacman -Ss marble-common
libre/marble-common 18.12.2-1.parabola1
Common libraries and plugins for Marble
extra/marble-common 18.12.2-1
Common libraries and plugins for Marble
</code></pre> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=113262019-02-12T15:40:15Zoaken-source
<ul></ul><p>it is. this will sort itself out with the next repo update tonight.</p> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=158302021-01-20T09:08:45Zbill-auger
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-9 priority-1 priority-lowest child" href="/issues/2965">Freedom Issue #2965</a>: [digikam]: depends on gt5-webengine</i> added</li></ul> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=175592022-05-08T13:48:08Zbill-auger
<ul><li><strong>Subject</strong> changed from <i>[marble]: depends on qt5-webengine</i> to <i>[marble][marble-common][marble-maps][marble-qt]: depends on qt5-webengine</i></li></ul><p>there are currently four packages built from the same PKGBUILD - they all need to be added to the blacklist though; because the webengine dependency is via marble-common, which the other three depend on</p>
<p>what i dont get, is what is the difference between 'marble' and 'marble-qt' - they are both QT programs with identical dependencies - "(Qt version)" does not seem to be meaningful</p>
<pre>
x86_64 Extra marble 22.04.0-2 Desktop Globe
x86_64 Extra marble-qt 22.04.0-2 Desktop Globe (Qt version)
</pre> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=175612022-05-08T13:57:29Zbill-auger
<ul><li><strong>Subject</strong> changed from <i>[marble][marble-common][marble-maps][marble-qt]: depends on qt5-webengine</i> to <i>[marble-common]: depends on qt5-webengine</i></li></ul> Packages - Freedom Issue #2117: [marble-common]: depends on qt5-webenginehttps://labs.parabola.nu/issues/2117?journal_id=175632022-05-08T14:29:59Zdllud
<ul></ul><p>Hi bill,</p>
<p>There is an alternative version of 'marble-common' in libre that I (sort of) maintain. I send a PR whenever it no longer works with the current marble version from Arch.</p>
<p>As such, besides 'marble-common', no other package needs to be blacklisted as they work with the 'marble-common' from libre. All in all, things are good as they are.</p>
<p>The difference between 'marble' and 'marble-qt' revolves around KDE integration. 'marble' has a deeper integration with KDE.</p>