summaryrefslogtreecommitdiffstats
path: root/aurweb/scripts/notify.py
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2018-05-18 02:44:51 +0200
committerLukas Fleischer <lfleischer@archlinux.org>2018-05-18 17:40:37 +0200
commit16795eaf467ef479dd0e37cce6f6623a59584e1f (patch)
tree2942c3da70fae235f54c7e652903a4cff5742552 /aurweb/scripts/notify.py
parentd24737f3f5b36b7dc541d2a00c0174e8105fb34a (diff)
downloadaur-16795eaf467ef479dd0e37cce6f6623a59584e1f.tar.gz
aur-16795eaf467ef479dd0e37cce6f6623a59584e1f.tar.xz
git-update: accept any arch in arch-dependent metadata
Currently we hardcode the architectures the official repos historically supported, which seems both inefficient because of hardcoding, and simply wrong, because many packages support various ARM platforms too. If we were to say "only officially supported arches will be supported in the AUR" we'd have to disable i686, which seems silly and arbitrarily restrictive. Also there's better places to implement such a blacklist (via die_commit in the main loop, via a config option to list supported arches, would make much more sense in terms of logic). As for the metadata extraction itself, there's no reason to hardcode the arches to check for at all. We can get this information too, from the .SRCINFO itself. Detecting this dynamically is not incompatible with a blacklist, should we ever decide to implement such a thing. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org>
Diffstat (limited to 'aurweb/scripts/notify.py')
0 files changed, 0 insertions, 0 deletions