You are not logged in.
How can a program build & installed with makepkg -si show up as 'Community' package?
Discovered this when I ran a dmenu script that shows which and how many packages are in each installed repo.
I then found out dmenu is listed as 'Community' which should be 'AUR'(in this script)
Some output for dmenu - patched version:
pacman -Qi dmenu |awk '/Version|Packager/ {print}'
Version : 5.0-1
Packager : qinohe
pacman -Sl | grep dmenu
community dmenu 5.0-1 [installed]
pacman -Qm | grep dmenu
....
Some output for community repo version:
pacman -Qi dmenu |awk '/Version|Packager/ {print}'
Version : 5.0-1
Packager : Levente Polyak <anthraxx@archlinux.org>
pacman -Sl | grep dmenu
community dmenu 5.0-1 [installed]
I'm running dmenu with some patches and am sure the patched version is what I'm using.
Dmenu is the only package showing this behavior, other apps installed with 'makepkg -si' show up when running 'pacman -Qm'
Last edited by qinohe (2021-04-27 15:54:50)
Offline
The issue is, that
pacman -Sl
lists packages available in the enabled repositories.
The flag "[installed]" is appended, if the package is installed as per the local pacman database.
So the output from pacman does not tell you, that the package is installed from the respective repository, but that a package with the given name is both available in the repository and is installed on your local machine.
macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }
Offline
So, shouldn't the installed package not be shown by 'pacman -Qm |grep dmenu'? or is it bound by that same rule?
Meaning, if I use the official PKGBUILD and add some patches, install with 'makepkg -si' it should show running 'pacman -Qm' or am I missing the point here?
Offline
There's no matching beyond the pkgname. If the name is the same, pacman assumes it's the same package.
Offline
There's no matching beyond the pkgname. If the name is the same, pacman assumes it's the same package.
Ah, that makes sense, better rename it next time, Thanks
Offline