On Fri, Apr 22, 2005, David M. Fetter wrote:
The noreplace rpmmacros addition works perfectly for us. It solves all
of our problems that we were having with auto-updating and working
configs being overwritten. However, the .rpmmacros existence causes
another side effect on linux systems because
The noreplace rpmmacros addition works perfectly for us. It solves all
of our problems that we were having with auto-updating and working
configs being overwritten. However, the .rpmmacros existence causes
another side effect on linux systems because it is seen by the OS rpm as
well as openpkg
On Sat, Apr 09, 2005, Shawn Walker wrote:
# ~/.rpmmacros:
%config config(noreplace)
This way all %config tags in the OpenPKG .spec files are on-the-fly
replaced with %config(noreplace) and as a result you get the .rpmnew
instead of .rpmsave files. Voila!
On Fri, Apr 08, 2005, Shawn Walker wrote:
On Apr 8, 2005 3:25 PM, David M. Fetter [EMAIL PROTECTED] wrote:
I agree with everything David wrote, and would at the very least like a flag I
can set in ~/.rpmmacros that would change this behaviour.
Well, this is already possible, of course:
On Apr 9, 2005 3:20 AM, Ralf S. Engelschall [EMAIL PROTECTED] wrote:On Fri, Apr 08, 2005, Shawn Walker wrote: On Apr 8, 2005 3:25 PM, David M. Fetter [EMAIL PROTECTED] wrote: I agree with everything David wrote, and would at the very least like a flag I can set in ~/.rpmmacros that would change
On Fri, 2005-04-08 at 20:59 +0200, Michael van Elst wrote:
On Fri, Apr 08, 2005 at 11:39:33AM -0700, David M. Fetter wrote:
It seems that when most of the rpms that have config files are upgraded,
the working config is moved to some *.rpmsave file and the new one is
put into place. What
On Fri, Apr 08, 2005, Michael van Elst wrote:
On Fri, Apr 08, 2005 at 11:39:33AM -0700, David M. Fetter wrote:
It seems that when most of the rpms that have config files are upgraded,
the working config is moved to some *.rpmsave file and the new one is
put into place. What this basically
