Arch Linux

The curl example in the BBS post is rediculous; just download the source yourself in the build() function if you are going to do that and then no md5sums are necessary.

The md5sum stuff getting in your way? Are you kidding me?
makepkg -g >> PKGBUILD && makepkg

Done.

I am not sure about this... as you point out, the "curl source" example is not great and actually adding md5sums is easy. But we do have an option to skip dependency checks and I think something similar could be done for checksums.

In the end, it is not on my to fix list but I would consider a patch.

To be honest, I have always resorted to commenting out the md5sums when bumping pkgver, because I had presupposed that adding another md5sum array at the end (with >>) would baffle makepkg. It appears that indeed it is not the case. Still, I believe adding such an option doesn't hurt anyone and makes things just a tad easier to handle for the end user.

And when you bump and bump and bump one PKGBUILD using makepkg -g >> PKGBUILD, you finally get a PKGBUILD with a lot of md5sums arrays. My PKGBUILDs for nvidia or opera-snapshot would have hundreds of lines ;-) All in all, just skipping checks seems a nicer option.

How's this? Adds option "-G/--warninteg" to only emit a warning if integrity checks are incomplete or missing. I changed the usage() function too, but not the manpage.

Here you go! Patched to add -n|--nohash option which bypasses integrity checks with warning if they are incomplete or missing.

lucke : if  FS#15051  was implemented, you wouldnt need to skip checks?

I prefer Profjim's patch, except I would keep the error in case of incomplete (whats the point of letting an incomplete checksums array in a pkgbuild...)
And -G option was mentioned for  FS#15051  so I don't know.

 FS#15051  would scratch my itch, indeed. Can't judge about other use cases, though.

I often have incomplete checksums in my own abs-based PKGBUILDS. What usually happens is I grab a PKGBUILD from abs, modify it in various ways, sometimes involving adding some of my own patches to the sources line, or adding some urls for extra documentation to the sources line, then go from there. I like to keep the PKGBUILDs as close to the originals as possible, hence I want to leave the old checksums there, and not to be ignored. At the same time, I might be tweaking my patches a lot, or I might not care if the checksums on the FAQ file I added to the sources change, so I usually leave the checksums off of these.

If my own mods are small enough, I can automate them using aur/customizepkg. It's a special pain to try to add in extra checksums using that tool; much easier just to add your own files to the end of the sources line (by default this tool adds new entries to the start of the sources line, but one can work around that).

The nice thing about customizepkg, for those who don't use it, is that any mods you've scripted through it are automatically detected and applied by yaourt the next time you install or upgrade that package (it will always force a mod-the-PKGBUILD-then-build-from-source).

here is my favorite version of this patch (and normally Dan's too)

That patch looks good to me. But it needs added to the manpage too.

I added man page on my maint-working branch :
http://code.toofishes.net/cgit/xavier/pacman.git/commit/?h=maint-working&id=8c53a95c5a3d8b680155f01bd9fc15b2dd284616

Looks good to me.