[pacman-dev] Adding a new config file to a package (e.g. mercurial file conflict)

[Jakob Gruber]

On 07/14/2011 07:44 PM, Dave Reisner wrote:
> On Thu, Jul 14, 2011 at 12:28:31PM -0500, Dan McGee wrote:
>> 3) Don't error at all, treat as a normal backup case except pretend
>> old file is the same as /dev/null (aka empty).
> This is where I sit. You shouldn't have to force the install, and the
> new file from the backup array should be dropped in place with a .pacnew
> extension. IMO, you get the best user experience going this route --
> you don't need to go out of your way to do the upgrade, and there's
> notification about the new file being dropped in. I don't think there's
> any need to create a different message. It's sort of a special case, but
> I don't think it needs any special handling.
>
> d

Agreed, this sounds like the right thing to do.