but I don’t know whether pamac runs in a separate/it’s own user context - and $HOME might not be set there.
It’s a warming - using /tmp is not a bad thing.
I’d ignore it after having investigated a bit the reason it is displayed.
I never saw this myself - can’t really help because I currently do not use Manjaro.
… in fact:
I almost never use pamac
only pacman - and yay for when I need the AUR
pamac can be configured to have its own $HOME, so to speak, and in the absence of such, it will use /tmp for compiling, linking and building the package. This is actually a good thing.
Then there we are.
I also installed it to look at the config/docs …
But neither exists after install.
So I still cant give a good config-based solution here … but I would encourage users to … you know … investigate the tool they have running.
Also as above … I dont know why you have it … it may be from rebuild-detector like in aragorns case … but its not a dependency of pamac.
I also dont know enough about it to tell you how to configure it or how its running…
But it stands to reason that if you didnt have parallel you wouldnt see that message.
To test I installed pamac and quickly built botsay, without parallel, and did not encounter the message.
Well you can look at the packages to see about them and their dependency chain.
As mentioned … its not pamac.
I have never seen it on KDE installs. But aragorn uses KDE and has it. Maybe from their own addition.
Maybe it came with your ISO. Maybe you installed something that relies on rebuild-detector.
I dont know … but I couldnt find either in the list of default packages.
Maybe also worth a note … I did a quick install of parallel just to see if that alone would impact pamac … and after doing another build job it did not. So the things are also ‘running’ somehow.