On Thu, 28 Jan 2010 16:59:16 +, Anton Shterenlikht
wrote:
> I've seen this behaviour for years, but never bothered
> to ask why.
>
> Imagine I already have in /etc/mail local .mc and .cf files. Imagine I
> then update freebsd.mc. When I run make nothing happens. What I think
> should happen i
On Jan 28, 2010, at 9:11 AM, Anton Shterenlikht wrote:
>> Because your carefully crafted local .mc files shouldn't be clobbered
>> whenever freebsd.mc is updated?
>
> I see.. so you are saying that freebsd.mc shouldn't even be
> touched at all, all local chages should be made straight
> to local .
On Thu, Jan 28, 2010 at 05:03:26PM +, Chris Rees wrote:
> On 28 January 2010 16:59, Anton Shterenlikht wrote:
> > I've seen this behaviour for years, but never bothered
> > to ask why.
> >
> > Imagine I already have in /etc/mail local .mc and .cf
> > files. Imagine I then update freebsd.mc. Wh
On 28 January 2010 16:59, Anton Shterenlikht wrote:
> I've seen this behaviour for years, but never bothered
> to ask why.
>
> Imagine I already have in /etc/mail local .mc and .cf
> files. Imagine I then update freebsd.mc. When I run make
> nothing happens. What I think should happen is that
> lo
I've seen this behaviour for years, but never bothered
to ask why.
Imagine I already have in /etc/mail local .mc and .cf
files. Imagine I then update freebsd.mc. When I run make
nothing happens. What I think should happen is that
local .mc should be updated and then .cf generated.
Because of this
