[aur-general] Package with arch-depending source
Hi, I'm maintaining a package in the AUR whose source is "arch-depending" (anaconda) For the moment I deal with that by putting the x86_64 version in the source/md5 array and adding a if [ "$CARCH" == "i686" ] (...) just after to modify it. Is that the usual way to do that? Or how should it be done? I see no information about that in the AUR guidelines. -- Ismael
On Mon, Feb 24, 2014 at 10:42 AM, Ismael Bouya <ismael.bouya@normalesup.org>wrote:
Hi,
I'm maintaining a package in the AUR whose source is "arch-depending" (anaconda)
For the moment I deal with that by putting the x86_64 version in the source/md5 array and adding a if [ "$CARCH" == "i686" ] (...) just after to modify it.
Is that the usual way to do that? Or how should it be done? I see no information about that in the AUR guidelines. -- Ismael
Yes it is, see the nvidia package for instance: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=p... Cheers, -- Maxime
(Mon, Feb 24, 2014 at 10:46:48AM +0100) Maxime Gauduin :
Yes it is, see the nvidia package for instance: https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=p...
Of course... It is always when I try to find an example file that I cannot find one... Thanks! Should I maybe add a section for this kind of example on the wiki? -- Ismael
On Mon, Feb 24, 2014 at 10:53 AM, Ismael Bouya <ismael.bouya@normalesup.org>wrote:
(Mon, Feb 24, 2014 at 10:46:48AM +0100) Maxime Gauduin :
Yes it is, see the nvidia package for instance:
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=p...
Of course... It is always when I try to find an example file that I cannot find one... Thanks!
Should I maybe add a section for this kind of example on the wiki? -- Ismael
Sure, it can't hurt having it documented, please do. -- Maxime
Sure, it can't hurt having it documented, please do.
I wanted to add it to the "Arch Packaging Standards" in the Architectures section, but... "You do not have permission to edit this page, for the following reason: This page has been protected to prevent editing or other actions." And I just found out that it is implicitly mentionned in the PKBUILD page (That we can access to the CARCH variable), but that's definitely not where I would expect to find this kind of information if I'm trying to think of how to do things correctly... -- Ismael
participants (2)
-
Ismael Bouya
-
Maxime Gauduin