Pacnew for initscripts in /etc/rc.d?

Question

I just updated iptables today and was surprised to find that my extensively customized /etc/rc.d/iptables initscript was silently overwritten.  I had expected pacman to create a .pacnew, as it does for anything that's modified in /etc, but this didn't happen.  (I also expected the .pacnew from my years as a Gentoo user.  Gentoo protects initscripts just like everything else in /etc.)
Is this intentional behaviour or is it a bug?  If intentional, is there any way I can force pacman to create .pacnew files instead?

Answer 1

My iptables script is significantly different from the default script.  The script supplied by the package assumes that the rules are static -- that they can be simply saved when the network goes down and restored when the network comes back up.
In my setup, I can't use the default script to achieve what I want, since my rules depend on my IP address.  (Explanation below if you're curious.)  I guess I just use iptables in a very non-standard way that's not quite supported.
I'd be happy to hear any suggestions for a better (more standard?) way of achieving what I'm doing.
Here's why my iptables rules depend on my IP address.  I have an OpenVPN tunnel to my office at the university.  To get access to university resources on my laptop while off campus, I route some of my traffic through my office.  For performance, when I'm on campus, I don't want this routing to happen (the OpenVPN server is out of town).  I route my traffic using a combination of iptables and iproute2: packets are marked using iptables's mangle table and conntrack capabilities, and iproute2 routes the marked packets over the VPN.  So, depending on my location (as determined by IP), my iptables mangle table is either empty or populated.