Hi list,<div><br></div><div>I am seeking some advice on the correct way to drop a patch that changes the name of the default configuration file for monit.</div><div><br></div><div>In Fedora, we carry a patch for monit that changes upstream&#39;s default configuration filename from /etc/monitrc to /etc/monit.conf. </div>

<div><br></div><div>Other than the fact that we have always carried the patch, I found no reason to carry it. Even though it is a small patch, in order to stay as close as possible to upstream, I want to drop it (and another one) in Rawhide.</div>

<div><br></div><div>The question is how to do this nicely. I see several options:</div><div><br></div><div>a) just drop the patch, breaking existing installations until the admin renames his configuration file, which will be annoying during F16 -&gt; F17 upgrades</div>

<div>b) moving a possibly existing /etc/monit.conf to /etc/monitrc in %post</div><div>c) symlinking /etc/monit.conf to /etc/monitrc if it exists in %post</div><div>d) moving a possibly existing /etc/monit.conf to /etc/monitrc and symlink it back to /etc/monit.conf </div>

<div>e) keep carrying the patch</div><div><br></div><div>Can someone give me some pointers here? Whichever option I choose, I&#39;d add a README.Fedora to explain the change to the RPM.</div><div><br></div><div>Thanks!</div>

<div><br clear="all">Maxim Burgerhout<br><a href="mailto:maxim@wzzrd.com" target="_blank">maxim@wzzrd.com</a><br>----------------<br>EB11 5E56 E648 9D99 E8EF 05FB C513 6FD4 1302 B48A<br>
</div><div><br></div>