Re: [arch-ports] PKGBUILD and package release thoughts

Do we really need more variables? Why not leave only one pkgrel number e.g. foo 1.0-1. If the x86_64 bit package needs a fix we would build only a 1.0-2 on x86_64 and let out not affected architectures. Next common release would be 1.0-3 for all archs.

Is it possible that way?

In the interest of keeping a single common PKGBUILD it sounds like Jason's solution would be the best, since it lets gensync/updatesync detect and pull the needed updates automatically. (If I understand correctly.) I don't even use ABS so I should probably shut-up, but since you asked . . . . . :) Maluvia