FS#7355 - [PATCH] Add an ignorearch option to makepkg
Attached to Project:
Pacman
Opened by Andreas Hauser (buggs) - Monday, 04 June 2007, 07:56 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 13 June 2007, 05:04 GMT
Opened by Andreas Hauser (buggs) - Monday, 04 June 2007, 07:56 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 13 June 2007, 05:04 GMT
|
Details
Since many PKGBUILD especially on aur miss a complete arch=
array, many people have edit the PKGBUILDs and add their
arch. Currently this affects mostly x86_64 and ppc users,
but as x86_64 gains popularity i686 are increasingly
affected.
An untested patch is appended as incentive. |
This task depends upon
Closed by Dan McGee (toofishes)
Wednesday, 13 June 2007, 05:04 GMT
Reason for closing: Implemented
Additional comments about closing: Added in GIT, pull it from there if you want it now, otherwise it will be in the 3.1 release.
Wednesday, 13 June 2007, 05:04 GMT
Reason for closing: Implemented
Additional comments about closing: Added in GIT, pull it from there if you want it now, otherwise it will be in the 3.1 release.
makepkg-ignorearch.patch
How hard is it to add an arch=() line anyway?
Let me guess you don't use x86_64 with a lot of aur?
I tell you it gets tiresome after 50 packages or so.
If i wanted that kind of bureaucracy i'd went for debian.
The way you do it, the default is "No i don't work on you arch"
while in reality most packages work without a problem.
So the default is not the common case, that's not good!
If you at least used a !$arch (like !x86_64) the work would be less.
Or change it to a warning not aborting the build.
The problem is that most people only use one architecture at a time.
I see your point though, but I don't know if making it non-fatal is a good idea. However, I do think a command line option may be acceptable, as you can't accidentally type "--ignorearch" - it is fairly explicit.
Side note though, your patch is backwards (your added lines are marked as removals with a minus). Also, the 'if' line would probably be better with:
if [ "$IGNORE_ARCH" = "0" -a ! in_array $CARCH ${arch[@]} ]; then
Could you test that out?
Attached is a tested (not reverted ;) patch.
It also changes the behaviour to still emit a warning even with ignore on.
Or in other words, the ignore arch flag changes the error from fatal to warning.
@space-m0nkey i get a 403 forbidden when accessing your git repo via the URL you gave.
I've merged your new patch into the branch.