On Thu, Dec 1, 2011 at 11:28 AM, Colin Guthrie <[email protected]> wrote: > 'Twas brillig, and Pascal Terjan at 01/12/11 10:19 did gyre and gimble: >> On Thu, Dec 1, 2011 at 09:58, Colin Guthrie <[email protected]> wrote: >>> Hi, >>> >>> There are times when the backup files from patches applied with >>> %apply_patches get in the way. It would be nice to be able to disable >>> backup file generation. e.g. with %apply_patches -n >>> >>> Can someone with the appropriate skills do this? I can't remember who >>> wrote this macro (I wrote the very crappy initial version of it and >>> someone else made it awesome!), but I have a feeling it was pterjan or >>> Annsi (or maybe it was pixel before he left...?). Anyway, it's a super >>> useful macro, but it would be really nice if it could avoid the backups. >> >> I think it was pixel > > Yeah, I think I remember now. It was a "parting gift" before he left :) > >>> Or another suggestion..... who actually uses these backup files? Perhaps >>> they can just be dropped completely? >> >> I use them when updating patches > > OK, so a more graceful way is needed to deal with the situation when the > patches are problematic (i.e. a dump installer just installing all the > files it finds. > > My work around is just a simple: > find -name "*.[0-9][0-9][0-9][0-9]" -delete > but it could be too greedy in some circumstances. > > So I guess an rpmmacro guru is needed. > > Col
i don't remember where ( but i will ask upstream) Panu wrote a mail explaining how to do like our %apply_patches but w/o the backups. So we can have 2 macros, ours ( that i will try to propose upstream ) and the one proposed by pany w/o the backups ?
