Hello. In the past there was someone who had pretty thoughtful overlay support. If you read this, please have a look. The thing is to me, the overlays start to produce quite a workload, and signatures cannot (easily) be used without proper overlay support. And without md5sum there is *no* verification that tarball checksums match etc etc. People, it would be *very* nice if pkgmk would gain a simple overlay support. This is really easy, i thought this: - pkgmk.conf: new $PKGMK_OVERLAY_DIR. Defaults to empty. - pkgmk: . new empty function stub "overlay() { ; }". . check existance of "$PKGMK_OVERLAY_DIR/$name/Overlay" if $PKGMK_OVERLAY_DIR is set, otherwise check for "Overlay" where we look for "Pkgfile". . if there is a match, source that, after Pkgfile. + optionally check whether overlay() is a shell function (as is done for build() of Pkgfile). . invoke "(set -e -x; overlay; build)" instead of "(set -e -x; build)". Like this Overlay can append to sources and renames, can overwrite build etc, but is otherwise not in the way. 'Seems to me, signature verification will still work (new files are simply not checked). The above should cumulate to a very small patch, add some for documentation. I will implement it and try it out, i also still have (and use) the zst support patch, so an overlay, anyway. If it works it is an easy way to allow overlays again; in the past it was easy, with md5sum (just replace Pkgfile entry me thinks), but with signatures it is all or nothing, so, in real life, it is nothing. Please, consider adding regular support for overlays. Thanks for your consideration. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)