Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#49232 - [steam] using depends_x86_64 instead of ${CARCH}

Attached to Project: Community Packages
Opened by Manuel (SunRed) - Friday, 06 May 2016, 10:39 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 01 October 2016, 03:47 GMT
Task Type General Gripe
Category Packages: Multilib
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I still don't understand why the steam package uses ${CARCH} to set the depends for x86_64 accordingly. ${CARCH} is only meant to be used in procedures like prepare, build, package and so on... Instead you can just define architecture specific dependencies with the depends_x86_64 and optdepends_x86_64 lists.

The PKGBUILD should therefore look like the following:
http://pastebin.com/8t866HAR
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 01 October 2016, 03:47 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Friday, 06 May 2016, 12:16 GMT
It does this because architecture specific variables have only been available for a short time. And $CARCH can be used anywhere, I have no idea where you came up with the idea it should only be used in the functions (yes, functions, not procedures).

Loading...