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
Opened by Manuel (SunRed) - Friday, 06 May 2016, 10:39 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 01 October 2016, 03:47 GMT
|
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
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).