On Sep 18, 2013, at 3:40 AM, Joshua Root <[email protected]> wrote: > On 2013-9-18 17:28 , [email protected] wrote: >> Hi devs, >> >> could it be advisable to have checksums also for every patch file associated >> with a certain port? >> (But this is probably not needed when the patch file is being pulled via svn >> or rsync from the MacPorts tree, because there everything is reviewable.) >> >> The situation should be different in case a patch file is pulled from >> external. >> In the back of my head I remember to have seen such cases in the past… >> At least in the guide I couldn't find anything about that. >> Could you point me to where this is documented? > > Checksums are required for all patchfiles that have to be downloaded > (i.e. don't live in files/). I don't know what the documentation is like > on this point.
I'm not sure there's any documentation. You could look at some Portfiles: http://trac.macports.org/browser/trunk/dports/editors/vim/Portfile?rev=110123#L62 http://trac.macports.org/browser/trunk/dports/python/py-oursql/Portfile?rev=111088#L42 There are probably others. Try grepping for "patch_sites". vq _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
