On Thu, Dec 29, 2005 at 04:03:02PM -0800, Jeremy C. Reed wrote:
> On Thu, 29 Dec 2005, Jeremy C. Reed wrote:
> 
> >You can use a MESSAGE.common for the common parts and then the 
> >MESSAGE.${OPSYS} for the specific parts. My own pkgsrc has a 
> >security/audit-packages/MESSAGE.NetBSD
> 
> The point is you don't have to add the MESSAGE related lines to the 
> Makefile, as it is done automatically.

Thanks, I'm aware of what you can do with MESSAGE file processing. 

What I was looking for with this commit was a way to say "do this for
every operating system except DragonFly", and I could see no easy way
of doing that.  I'd be happy to be proved wrong.

I also don't see any real need for it to be changed since we've had
the MESSAGE handling in its present form for some time now, and this
is the first exception we've found.
 
> >I also have this patch (in my new MESSAGE.common but based on old MESSAGE):
> 
> Sorry, it was reversed. Here again:
> 
>  You may wish to have the vulnerabilities file downloaded daily so that
> -it remains current.  This may be done by adding an appropriate entry
> -to the root users crontab(5) entry.  For example the entry
> +it remains current.  This may be done by adding an appropriate crontab(5)
> +entry.  For example the entry

This also needs to be done for operating systems like Solaris, where I
strongly doubt there's any /etc/security.local, although I admit I
haven't looked lately.

Regards,
Alistair