Thanks, I pacman -Syu again after reading your post and it updated.
which is super weird, because I am doing this on a vm which was recreated about 2 hours or so ago ( I just saved a snapshot of clean post installation, so I can reproduce the steps or startover again and again ) , and installed the -git versions.
That keyring is the arch kde package dev. (Antonio Rojas is who makes the kde packages on arch). Should be installed by default.
I then moved on to a dragonized clone. Didn’t spent much time on barebones. was just more of a test. Because I want to come up with a list of missing packages for dragonfire and islandcoder.
There are some little details with dragonized edition and kde git though
So now I am concentrating on dragonized version and kde-git.
Maybe the dragonized style can be kept on kde-git, since so far its working well.
Some issues:
breeze-icons-git and latte-dock-git conflict because of latte-dock's icon
partition-manager-git installs kpmcore-git , which then conflits when buildiso tries to install kpmcore
I suspect that is because I don't run the garuda assistant after update, but its necessary to do a pacman-key --populate . tray icon garuda app with "fix keyring" doesn't fix it also.
strangelly, it doesn't have the bugs that I had when I tried it the last time on my live garuda system. Will have a go at it latter tonight after doing some snapshots ( on the live system, i mean. I am installing the kde-git iso into a qemu vm ).
@dr460nf1r3 Do you mind if I try to create an iso that installs kde-git-meta, instead of only the git versions of what dragonized edition installs ? ( or maybe try to create a kde-git-base-meta , so that its not so bloated ?? )
( again posted this on the wrong page ... damn i am dumb )
This started happening today. In which package should the icon actually reside? I can ix this easily.
Which package pulls in the non-git kpmcore?
This would probably be preferred, as we would have a lot of git/non-git mixed kf5/plasma packages otherwise? I created the metapkg for this purpose. PKGBUILD is located here and can be easily adjusted for base-meta, which I think is a good idea to have.
good question. Can the PKGBUILD on lattedock be made to check if the icon is already present and only install if not ?
will check out which one it is.
How does one use custom PKGBUILDS for buildiso (replacing the normal ones) ? I would like to try customizing some and test.
Yes, but I suspecting it should be either an easy fix (some ~/.config file or ~/.cache issue) or kde bug report. … I hope … ( applying another color ( even if the same ) fix it, but restarting happens again… ) will try to fix it later tonight !
It will happen from time to time, kde git breaking either theming or latte-dock.
Its not common, but probably happens.
Dunno if we should try to keep the styles the same, possibly only going more "vanilla" when everything breaks, or "just go vanilla and not worry".
Also maybe this is a non issue, because if its a kde bug, its just a matter of reporting it and they fixing it I mean ... using kde-git ... one has to learn to live with bugs ( ...cof cof even using kde-not-git ... cof cof )
If this is intended as an “edge” edition then it should be vanilla. No custom theming, no Latte, etc. This way it can be used for testing KDE and as a barebones option too.
Is it ok to try to mimick latte’s behaviour, but with “normal standard kde panel’s” ?
I did this sometimes ( when latte didn’t work with kde git )… its not the same usuability, not really, but kinda works