You are not logged in.
why do the lib32 packages from community not have the CARCH suffix, ie the ...-x86_64.pkg.tar.gz?
for example:
ls /var/cache/pacman/pkg/lib32-*
/var/cache/pacman/pkg/lib32-alsa-lib-1.0.20-1.pkg.tar.gz
/var/cache/pacman/pkg/lib32-libdrm-2.4.11-2.pkg.tar.gz
/var/cache/pacman/pkg/lib32-libxrandr-1.3.0-1.pkg.tar.gz
/var/cache/pacman/pkg/lib32-atk-1.26.0-1.pkg.tar.gz
/var/cache/pacman/pkg/lib32-libgcrypt-1.4.4-1.pkg.tar.gz
/var/cache/pacman/pkg/lib32-libxrender-0.9.4-2.pkg.tar.gz
...ps: i know, these packages are only available for the x86_64 architecture. but isn't it usual and common sense to add CARCH to the package?
Last edited by DonVla (2009-07-07 10:42:00)
Offline
No [community] packages have it...
Offline
No [community] packages have it...
oh, that's true!
why?
Offline
For some reason the community database scripts were never updated to handle it. This will change soon when the community repo moves to using the same scripts as the core & extra repos.
Offline
thanks allan!
Offline