On Thu, 2007-11-15 at 22:00 +0000, Stuart Henderson wrote: > On 2007/11/15 23:04, Soner Tari wrote: > > I've checked the other options like the one you are mentioning, but > > handling this in a separate shell script seems better to me (for example > > it's more readable and manageable in my opinion). Also note that I took > > postfix files as the basis for my p3scan-config. Therefore, if there is > > no harm, I'd like to keep p3scan-config. > > This is the wrong way to go, the pkg_* tools can handle this, so > let them. @exec is useful for cases where you can't use the normal > mechanisms, it's available but it should almost never be necessary. > You don't see it used very much in our ports tree. > > Postfix has to populate the chroot with files from the installed > system, and has its own mechanism to upgrade config files between > versions via /etc/postfix/post-install. This goes to make it a > bit of a special case... but even so, it does use the standard > @extra mechanism so that it doesn't break pkg_delete -c.
Please find attached the last version based on your input. (My nice custom messages to the user are gone now, but anyway. Also, @sample cannot handle symlinks correctly, so I had to use @exec for it, hope that's ok.) Btw, net category is back, because the proxy software I see in the tree include net among their categories too, see pop3gwd for an example.
p3scan-2.3.2.tar.gz
Description: application/compressed-tar
