On Fri, May 22, 2015 at 08:38:22AM -0400, Andrew Gregory wrote:
Would it not make more sense to just return 0 for this? Presumably if a user or script is running makepkg without --force they don't care whether the package is newly built or already existed. Is there actually a use case where a user would care if the package had already been built but would not run with --force to begin with?
apg
The reason I use it in this way is for automated build scripts to be able to rely on makepkg to figure out if a package of this specific version has already been built or not and give me the appropriate message in the log. Otherwise I would have to parse makepkg's output to know that the package didn't fail te build, it refused to. And checking outside of makepkg would require duplicating some code.