Package Details: kparts-git 6.0.0_r822.g2d6ed3f-1

Git Clone URL: (read-only, click to copy)
Package Base: kparts-git
Description: Document centric plugin system
Upstream URL:
Licenses: LGPL-3.0-only, LGPL-2.0-only
Groups: kf6-git
Conflicts: kparts
Provides: kparts
Submitter: ilpianista
Maintainer: IslandC0der (chaotic-aur)
Last Packager: IslandC0der
Votes: 16
Popularity: 0.000000
First Submitted: 2014-01-04 11:37 (UTC)
Last Updated: 2024-03-01 06:49 (UTC)

Latest Comments

MarsSeed commented on 2023-10-24 13:37 (UTC) (edited on 2023-10-24 13:38 (UTC) by MarsSeed)

Needs dependencies like kde-unstable/kparts (plus 'git', and the git version of ECM):

arojas commented on 2014-03-20 20:02 (UTC)

ok, hopefully they will keep BIC after the beta is released next week

ant32 commented on 2014-03-20 15:35 (UTC)

While updating my computer using the repo I now had to force reinstall kparts-git if I didn't want it to simply crash.

ant32 commented on 2014-03-20 15:10 (UTC)

Doesn't the error message that I posted state what went wrong? (The error occured while building some of the packages that depend on kparts-git). Doesn't it say that KXMLGUI made a change and now this package needs to be rebuild? I already did rebuild this package in my repo and afterwards the packages depending on this package work. Kparts received the last git commit on March 1.

arojas commented on 2014-03-20 07:21 (UTC)

@ant32 When you build the package you always get the latest git revision (regardless of what the version number is in AUR) and the version number of the package is automatically updated, so if you rebuild it and get the same version number it means that nothing has changed upstream and it is safe to keep the same package. There's no need to manually raise the pkgver. I'm not sure why compilation failed for you if you did it that way. Maybe you didn't compile them in the right order?

ant32 commented on 2014-03-20 04:06 (UTC)

I was building everything every time but only updateing when the name of the compiled package changed. Would you suggest I rename the file or simply replace it and have the user get messages that the pkg they have is corrupt once they for some reason uninstalled everything and reinstalled? For the mingw-w64 repo that I manage I more times recompiled packages and when i did I would simply rename the package by adding "_1" eg. qt4-4.8.5-5-x86_64_1.pkg.tar.xz. 1. Should I rename the file if the git version did not change since last time I compiled? 2. Should I modify the pkgver from pkgver=1 to pkgver=1a then next time to 1b etc? (This way the user would update to the last build every time he updated.) 3. Should I only rebuild once per week so users aren't asked to update every day? 4. Am I wasting my time with providing a repo for people? My view was by providing a repo I made it easier for people to test. And by rebuilding it often and in a clean chroot I was helping detecting missing dependencies and build errors earlier. There seem to be many users who don't comment if things are broken.

arojas commented on 2014-03-19 19:44 (UTC)

@ant32 you should force updating all kf5 packages to the latest git revision when you update some package in your repo, even if it hasn't been updated in AUR. These packages depend heavily on one another and even if it compiles fine, problems could arise if you use different git revisions of different packages together.

ant32 commented on 2014-03-19 14:45 (UTC)

There are a couple packages that depend on this package that are failing to compile. Could you bump up the pkgrel? /opt/kf5/lib/ undefined reference to `KXmlGuiWindow::applyMainWindowSettings(KConfigGroup const&, bool)' collect2: error: ld returned 1 exit status If I shouldn't ask for something like this please tell me. Or if this problem has to do with something else. There hasn't been an update to this package for a while so it doesn't get updated in my repo