Re: pkgsrc/mail/sendmail anomalies

[Richard PALO <richard.palo%free.fr@localhost>]

Well, this is encouraging...
I took a look at what NetBSD modified in devtools/OS/NetBSD, and judging 
by site.config.m4, I tried the following :

- removed PKG_DESTDIR_SUPPORT=destdir

- fixed a problem with INSTALLATION_DIRS (probably only noticed on SunOS 
with smf support enabled)
> -INSTALLATION_DIRS=     bin lib sbin
> +INSTALLATION_DIRS+=    bin lib sbin

- quickly tried the following as a test

> diff --git a/mail/sendmail/files/site.config.m4 
> b/mail/sendmail/files/site.config.m4
> index 26bbdd4..4db3fe4 100644
> --- a/mail/sendmail/files/site.config.m4
> +++ b/mail/sendmail/files/site.config.m4
> @@ -29,6 +29,11 @@ define(`confLIBOWN', `${BINOWN}')
>  define(`confLIBGRP', `${BINGRP}')
>  define(`confINCOWN', `${SHAREOWN}')
>  define(`confINCGRP', `${SHAREGRP}')
> +define(`confSBINGRP', `${BSD_BINGRP}')
> +define(`confUBINOWN', `${BSD_BINOWN}')
> +define(`confUBINGRP', `${BSD_BINGRP}')
> +define(`confMANOWN', `${BSD_MANOWN}')
> +define(`confMANGRP', `${BSD_MANGRP}')
>
>  # have libmilter use poll(2) instead of select(2)
>  # XXX all supported systems should support poll(2), if one is discovered

This allowed the seemingly normal destdir processing to proceed.

BTW, I fail to see the significance using BSD_BINGRP, BSD_BINOWN, etc..
Is there a particular reason BINGRP, BINOWN, etc can't be simply used?

Finally, would it not be better to actually use the site.config.m4 (as I 
merely tested here) to set these as opposed to patching 
devtools/OS/<platform>?  That is, this is, after all, pkgsrc and 
according to the sendmail docs, that is recommended policy.